About task-generator
A skill that turns an atomic feature slice into a detailed Markdown task for engineers or coding agents. It covers backend, frontend, and infrastructure work, with requirements, dependencies, implementation guidance, and validation criteria.
Key features
- 01Generates numbered task Markdown files
- 02Covers backend, frontend, and infrastructure
- 03Uses architecture and harness rules
- 04Includes layer-specific implementation guidance
- 05Records dependencies and validation criteria
Use cases
- 01Breaking a feature into implementable task slices
- 02Preparing frontend tasks with data-testid contracts
- 03Ordering backend and frontend tasks around API dependencies
- 04Documenting implementation and validation requirements
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/task-generatorin Claude Code to confirm it loaded.
Bundled filesevals/evals.jsonreferences/task-schema.md
Details
From the project READMETask Generator
Convert one atomic slice of a Feature into a detailed task-NNN-slug.md for engineers or coding agents.
Harness discovery
See ../nextstage-harness/references/harness-discovery.md. Load rules from {harness_root}/rules/*.md. Read architecture-rules.md first. Legacy: .cursor/rules/*.mdc only if {harness_root} is absent. Read requirements.md strictly — do not invent tables or endpoints.
Scope
- Layers: Backend, Frontend, Infrastructure
- Not this skill: E2E →
e2e-test-generator; Backend unit tests →unit-test-task-generator
Golden rule
No one-line summaries. The implementer must know what to do, where (probable paths), which stack/rules apply, and validation criteria. Never repeat the summary verbatim in the detailed section.
Inputs
- Atomic task description (from orchestrator)
- Layer type: Backend | Frontend | Infra
{product_root}/docs/versions/{version_san}/requirements.md- Task number
NNNand dependency tasks
Dependencies
- FK parents before children — task order reflects migration/API order
- Frontend consuming an API → backend task precedes frontend task
- See
references/task-schema.mdfor full file template
Classification
- Error — bug in existing feature
- Improvement — behavior change to existing feature
- Implementation — new feature
Frontend extras
When task touches UI:
- data-testid contract — kebab-case, prefixed (
btn-,input-,form-, etc.) - Auth forms: marketing panel, PasswordInput, i18n keys per frontend rules when present
- i18n: all strings via translation keys;
useFormat()for dates/currency - Navigation:
groupKeywhen adding menu items (if nav rules exist)
Backend extras
When uses_grogoo: false (default): Sanctum, manual modules — no Grogoo references.
When multitenancy: explicit company_id / ownership validation in criteria.
Output path
{product_root}/docs/versions/{version_san}/tasks/task-NNN-slug.md
For subversions: under subversions/{subversion_san}/tasks/.
References
| File | When |
|---|---|
references/task-schema.md | Full markdown template and header fields |
Related skills
unit-test-task-generator— after backend implementation taskse2e-test-generator— after frontend tasks with UIexecution-handoff-generator— after all tasks for the version are written (planning closure)