Vibecode Workelo
track this build5 steps, step by step0%KINDA · weekend project
Strip away the branding and Workelo is a workflow engine: journey templates, tasks with owners and due dates relative to a start date, reminders, and a page the new hire actually sees. That part is genuinely a weekend build, and for a five person company a self-hosted version is fine. What breaks is everything at the edges: HRIS sync, Google Workspace and Slack account provisioning, equipment requests routed to IT, document signing, and the audit trail HR wants when someone leaves. Also worth naming the obvious: this is a tool for coordinating other people, so a personal build only pays off if you are the one running onboarding. If you are, you get most of the value; if you need it to talk to your HRIS, you will spend the weekend on OAuth instead of features.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Workelo. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Workelo indie build ## Goal Build the smallest trustworthy replacement for the core Workelo workflow for one developer or a tiny team. ## Scope A self-hosted app where you define onboarding and offboarding journey templates as tasks offset from a start date, launch one per employee, assign owners, and email everyone their overdue items daily. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - HRIS and ATS connectors, so employee records get typed in by hand - Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit - E-signature and document collection flows that a legal team will accept - The polished employee-facing portal and email design that makes day one feel intentional rather than homemade - Reporting, audit logs, and the GDPR paperwork story your HR lead will ask about If those capabilities are essential, use Workelo instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a self-hosted employee onboarding and offboarding tracker. Empty folder, no scaffolding questions, just build it. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, SQLite through Prisma, Tailwind for styling, server actions for all mutations. No external auth provider. No telemetry. No analytics. Data model: - Journey template: name, type (onboarding, crossboarding, offboarding), list of TaskTemplates. - TaskTemplate: title, description (markdown), owner role (manager, hr, it, employee), dayOffset (integer, negative means before the start or exit date), optional link. - Employee: name, personal email, work email, role, manager name, manager email, startDate, exitDate (nullable), status. - Journey: created by applying a template to an employee, snapshots the tasks so later template edits do not rewrite history. - Task: title, description, ownerEmail resolved at launch, dueDate computed from dayOffset plus the anchor date, done flag, completedAt. Features in scope: - CRUD for templates with a drag free ordering (just an integer sort field and up/down buttons). - Launch a journey: pick employee plus template, preview computed due dates, confirm. - Dashboard: all active journeys, percent complete, overdue count, sorted by nearest due date. - Per journey view grouped by week relative to the anchor date, checkboxes that complete tasks via server actions. - A tokenized public task page at /me/[token] so a new hire or manager can see and tick their own tasks without an account. Token is a random 32 char string on the journey, unguessable, no login. - A daily digest script (npm run digest) that finds tasks due or overdue and emails each owner one summary. Use nodemailer with SMTP_HOST, SMTP_USER, SMTP_PASS, MAIL_FROM from .env. If those are unset, print the emails to stdout instead of failing. - Seed script with one realistic onboarding template (about 15 tasks spanning day -7 to day +30) and one offboarding template (about 10 tasks). Explicitly out of scope: HRIS or ATS integrations, Slack or Google Workspace provisioning, e-signature, file uploads, multi tenancy, role based admin permissions. One admin, protected by a single ADMIN_PASSWORD in .env checked in middleware with a cookie. That is enough. Deliver a README with setup, .env.example, prisma migrate command, and a cron line for the digest. Make the /me pages look decent on a phone; that is the only surface an employee ever sees. ## Required capabilities - Node 20 and a place to run it (a small VPS or a container) - SMTP credentials for reminder emails, or nothing if you accept an in-app inbox only - Someone willing to keep the templates current, which is the actual work ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Workelo. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Workelo indie build ## Goal Build the smallest trustworthy replacement for the core Workelo workflow for one developer or a tiny team. ## Scope A self-hosted app where you define onboarding and offboarding journey templates as tasks offset from a start date, launch one per employee, assign owners, and email everyone their overdue items daily. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - HRIS and ATS connectors, so employee records get typed in by hand - Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit - E-signature and document collection flows that a legal team will accept - The polished employee-facing portal and email design that makes day one feel intentional rather than homemade - Reporting, audit logs, and the GDPR paperwork story your HR lead will ask about If those capabilities are essential, use Workelo instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a self-hosted employee onboarding and offboarding tracker. Empty folder, no scaffolding questions, just build it. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, SQLite through Prisma, Tailwind for styling, server actions for all mutations. No external auth provider. No telemetry. No analytics. Data model: - Journey template: name, type (onboarding, crossboarding, offboarding), list of TaskTemplates. - TaskTemplate: title, description (markdown), owner role (manager, hr, it, employee), dayOffset (integer, negative means before the start or exit date), optional link. - Employee: name, personal email, work email, role, manager name, manager email, startDate, exitDate (nullable), status. - Journey: created by applying a template to an employee, snapshots the tasks so later template edits do not rewrite history. - Task: title, description, ownerEmail resolved at launch, dueDate computed from dayOffset plus the anchor date, done flag, completedAt. Features in scope: - CRUD for templates with a drag free ordering (just an integer sort field and up/down buttons). - Launch a journey: pick employee plus template, preview computed due dates, confirm. - Dashboard: all active journeys, percent complete, overdue count, sorted by nearest due date. - Per journey view grouped by week relative to the anchor date, checkboxes that complete tasks via server actions. - A tokenized public task page at /me/[token] so a new hire or manager can see and tick their own tasks without an account. Token is a random 32 char string on the journey, unguessable, no login. - A daily digest script (npm run digest) that finds tasks due or overdue and emails each owner one summary. Use nodemailer with SMTP_HOST, SMTP_USER, SMTP_PASS, MAIL_FROM from .env. If those are unset, print the emails to stdout instead of failing. - Seed script with one realistic onboarding template (about 15 tasks spanning day -7 to day +30) and one offboarding template (about 10 tasks). Explicitly out of scope: HRIS or ATS integrations, Slack or Google Workspace provisioning, e-signature, file uploads, multi tenancy, role based admin permissions. One admin, protected by a single ADMIN_PASSWORD in .env checked in middleware with a cookie. That is enough. Deliver a README with setup, .env.example, prisma migrate command, and a cron line for the digest. Make the /me pages look decent on a phone; that is the only surface an employee ever sees. ## Required capabilities - Node 20 and a place to run it (a small VPS or a container) - SMTP credentials for reminder emails, or nothing if you accept an in-app inbox only - Someone willing to keep the templates current, which is the actual work ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Workelo. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Workelo product brief ## Problem Strip away the branding and Workelo is a workflow engine: journey templates, tasks with owners and due dates relative to a start date, reminders, and a page the new hire actually sees. That part is genuinely a weekend build, and for a five person company a self-hosted version is fine. What breaks is everything at the edges: HRIS sync, Google Workspace and Slack account provisioning, equipment requests routed to IT, document signing, and the audit trail HR wants when someone leaves. Also worth naming the obvious: this is a tool for coordinating other people, so a personal build only pays off if you are the one running onboarding. If you are, you get most of the value; if you need it to talk to your HRIS, you will spend the weekend on OAuth instead of features. ## Product outcome A self-hosted app where you define onboarding and offboarding journey templates as tasks offset from a start date, launch one per employee, assign owners, and email everyone their overdue items daily. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20 and a place to run it (a small VPS or a container) - SMTP credentials for reminder emails, or nothing if you accept an in-app inbox only - Someone willing to keep the templates current, which is the actual work ## Explicit non-goals for v1 - HRIS and ATS connectors, so employee records get typed in by hand - Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit - E-signature and document collection flows that a legal team will accept - The polished employee-facing portal and email design that makes day one feel intentional rather than homemade - Reporting, audit logs, and the GDPR paperwork story your HR lead will ask about ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a self-hosted employee onboarding and offboarding tracker. Empty folder, no scaffolding questions, just build it. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, SQLite through Prisma, Tailwind for styling, server actions for all mutations. No external auth provider. No telemetry. No analytics. Data model: - Journey template: name, type (onboarding, crossboarding, offboarding), list of TaskTemplates. - TaskTemplate: title, description (markdown), owner role (manager, hr, it, employee), dayOffset (integer, negative means before the start or exit date), optional link. - Employee: name, personal email, work email, role, manager name, manager email, startDate, exitDate (nullable), status. - Journey: created by applying a template to an employee, snapshots the tasks so later template edits do not rewrite history. - Task: title, description, ownerEmail resolved at launch, dueDate computed from dayOffset plus the anchor date, done flag, completedAt. Features in scope: - CRUD for templates with a drag free ordering (just an integer sort field and up/down buttons). - Launch a journey: pick employee plus template, preview computed due dates, confirm. - Dashboard: all active journeys, percent complete, overdue count, sorted by nearest due date. - Per journey view grouped by week relative to the anchor date, checkboxes that complete tasks via server actions. - A tokenized public task page at /me/[token] so a new hire or manager can see and tick their own tasks without an account. Token is a random 32 char string on the journey, unguessable, no login. - A daily digest script (npm run digest) that finds tasks due or overdue and emails each owner one summary. Use nodemailer with SMTP_HOST, SMTP_USER, SMTP_PASS, MAIL_FROM from .env. If those are unset, print the emails to stdout instead of failing. - Seed script with one realistic onboarding template (about 15 tasks spanning day -7 to day +30) and one offboarding template (about 10 tasks). Explicitly out of scope: HRIS or ATS integrations, Slack or Google Workspace provisioning, e-signature, file uploads, multi tenancy, role based admin permissions. One admin, protected by a single ADMIN_PASSWORD in .env checked in middleware with a cookie. That is enough. Deliver a README with setup, .env.example, prisma migrate command, and a cron line for the digest. Make the /me pages look decent on a phone; that is the only surface an employee ever sees. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Workelo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Workelo indie build ## Goal Build the smallest trustworthy replacement for the core Workelo workflow for one developer or a tiny team. ## Scope A self-hosted app where you define onboarding and offboarding journey templates as tasks offset from a start date, launch one per employee, assign owners, and email everyone their overdue items daily. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - HRIS and ATS connectors, so employee records get typed in by hand - Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit - E-signature and document collection flows that a legal team will accept - The polished employee-facing portal and email design that makes day one feel intentional rather than homemade - Reporting, audit logs, and the GDPR paperwork story your HR lead will ask about If those capabilities are essential, use Workelo instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a self-hosted employee onboarding and offboarding tracker. Empty folder, no scaffolding questions, just build it. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, SQLite through Prisma, Tailwind for styling, server actions for all mutations. No external auth provider. No telemetry. No analytics. Data model: - Journey template: name, type (onboarding, crossboarding, offboarding), list of TaskTemplates. - TaskTemplate: title, description (markdown), owner role (manager, hr, it, employee), dayOffset (integer, negative means before the start or exit date), optional link. - Employee: name, personal email, work email, role, manager name, manager email, startDate, exitDate (nullable), status. - Journey: created by applying a template to an employee, snapshots the tasks so later template edits do not rewrite history. - Task: title, description, ownerEmail resolved at launch, dueDate computed from dayOffset plus the anchor date, done flag, completedAt. Features in scope: - CRUD for templates with a drag free ordering (just an integer sort field and up/down buttons). - Launch a journey: pick employee plus template, preview computed due dates, confirm. - Dashboard: all active journeys, percent complete, overdue count, sorted by nearest due date. - Per journey view grouped by week relative to the anchor date, checkboxes that complete tasks via server actions. - A tokenized public task page at /me/[token] so a new hire or manager can see and tick their own tasks without an account. Token is a random 32 char string on the journey, unguessable, no login. - A daily digest script (npm run digest) that finds tasks due or overdue and emails each owner one summary. Use nodemailer with SMTP_HOST, SMTP_USER, SMTP_PASS, MAIL_FROM from .env. If those are unset, print the emails to stdout instead of failing. - Seed script with one realistic onboarding template (about 15 tasks spanning day -7 to day +30) and one offboarding template (about 10 tasks). Explicitly out of scope: HRIS or ATS integrations, Slack or Google Workspace provisioning, e-signature, file uploads, multi tenancy, role based admin permissions. One admin, protected by a single ADMIN_PASSWORD in .env checked in middleware with a cookie. That is enough. Deliver a README with setup, .env.example, prisma migrate command, and a cron line for the digest. Make the /me pages look decent on a phone; that is the only surface an employee ever sees. ## Required capabilities - Node 20 and a place to run it (a small VPS or a container) - SMTP credentials for reminder emails, or nothing if you accept an in-app inbox only - Someone willing to keep the templates current, which is the actual work ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Workelo product brief ## Problem Strip away the branding and Workelo is a workflow engine: journey templates, tasks with owners and due dates relative to a start date, reminders, and a page the new hire actually sees. That part is genuinely a weekend build, and for a five person company a self-hosted version is fine. What breaks is everything at the edges: HRIS sync, Google Workspace and Slack account provisioning, equipment requests routed to IT, document signing, and the audit trail HR wants when someone leaves. Also worth naming the obvious: this is a tool for coordinating other people, so a personal build only pays off if you are the one running onboarding. If you are, you get most of the value; if you need it to talk to your HRIS, you will spend the weekend on OAuth instead of features. ## Product outcome A self-hosted app where you define onboarding and offboarding journey templates as tasks offset from a start date, launch one per employee, assign owners, and email everyone their overdue items daily. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20 and a place to run it (a small VPS or a container) - SMTP credentials for reminder emails, or nothing if you accept an in-app inbox only - Someone willing to keep the templates current, which is the actual work ## Explicit non-goals for v1 - HRIS and ATS connectors, so employee records get typed in by hand - Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit - E-signature and document collection flows that a legal team will accept - The polished employee-facing portal and email design that makes day one feel intentional rather than homemade - Reporting, audit logs, and the GDPR paperwork story your HR lead will ask about ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a self-hosted employee onboarding and offboarding tracker. Empty folder, no scaffolding questions, just build it. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, SQLite through Prisma, Tailwind for styling, server actions for all mutations. No external auth provider. No telemetry. No analytics. Data model: - Journey template: name, type (onboarding, crossboarding, offboarding), list of TaskTemplates. - TaskTemplate: title, description (markdown), owner role (manager, hr, it, employee), dayOffset (integer, negative means before the start or exit date), optional link. - Employee: name, personal email, work email, role, manager name, manager email, startDate, exitDate (nullable), status. - Journey: created by applying a template to an employee, snapshots the tasks so later template edits do not rewrite history. - Task: title, description, ownerEmail resolved at launch, dueDate computed from dayOffset plus the anchor date, done flag, completedAt. Features in scope: - CRUD for templates with a drag free ordering (just an integer sort field and up/down buttons). - Launch a journey: pick employee plus template, preview computed due dates, confirm. - Dashboard: all active journeys, percent complete, overdue count, sorted by nearest due date. - Per journey view grouped by week relative to the anchor date, checkboxes that complete tasks via server actions. - A tokenized public task page at /me/[token] so a new hire or manager can see and tick their own tasks without an account. Token is a random 32 char string on the journey, unguessable, no login. - A daily digest script (npm run digest) that finds tasks due or overdue and emails each owner one summary. Use nodemailer with SMTP_HOST, SMTP_USER, SMTP_PASS, MAIL_FROM from .env. If those are unset, print the emails to stdout instead of failing. - Seed script with one realistic onboarding template (about 15 tasks spanning day -7 to day +30) and one offboarding template (about 10 tasks). Explicitly out of scope: HRIS or ATS integrations, Slack or Google Workspace provisioning, e-signature, file uploads, multi tenancy, role based admin permissions. One admin, protected by a single ADMIN_PASSWORD in .env checked in middleware with a cookie. That is enough. Deliver a README with setup, .env.example, prisma migrate command, and a cron line for the digest. Make the /me pages look decent on a phone; that is the only surface an employee ever sees. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Workelo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
HR teams are not buying a task list, they are buying the fact that a start date in the HRIS makes eleven things happen across six systems without anyone remembering to do them. That plumbing is unglamorous, breaks silently, and needs an owner when it does. Add the compliance and audit angle for offboarding, plus the fact that the buyer is usually a two person People team with zero engineering budget, and a self-hosted alternative loses on total cost even when it wins on features.
xHRIS and ATS connectors, so employee records get typed in by hand
xAutomatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit
xE-signature and document collection flows that a legal team will accept
xThe polished employee-facing portal and email design that makes day one feel intentional rather than homemade
xReporting, audit logs, and the GDPR paperwork story your HR lead will ask about
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Workelo with one prompt"
Vibecode Workelo
Kinda. The core of Workelo is buildable in a weekend with the prompt on this page, but there are real gaps: HRIS and ATS connectors, so employee records get typed in by hand, Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit. Read the honest list above before committing.
How much does Workelo cost?
Workelo's pricing is usage-based or varies by plan · No published price anywhere on the site; /en/pricing returns 404, CTAs are "Demander une demo" and free trial.
What do I lose by replacing Workelo?
Honestly: HRIS and ATS connectors, so employee records get typed in by hand; Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit; E-signature and document collection flows that a legal team will accept; The polished employee-facing portal and email design that makes day one feel intentional rather than homemade; Reporting, audit logs, and the GDPR paperwork story your HR lead will ask about. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Workelo?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.