task-preparation
Task Preparation
Use after roadmap structure exists and one concrete task already exists in docs/tasks/ and is selected or selectable from confirmed roadmap state.
Owns task-local spec.md, optional plan.md, review pauses, routine follow-up, and execution handoff context. It consumes an existing roadmap-layer task; it does not create task directories, author task.md, or reshape roadmap structure.
Required Gates
| Gate | Required behavior |
|---|---|
| Task selection | Enter only when an existing concrete task is selected or clearly next from confirmed roadmap state. If milestone confirmation, task selection, or dependencies are still ambiguous, stop and use milestone-planning. |
| Governance mode | Docs governance changes roadmap/docs only and does not authorize code. |
| Spec | One task-local spec.md defines behavior, scope, exclusions, and tradeoffs. Default 1 task -> 1 spec; revise instead of duplicating. |
| Plan | Default no plan.md. Create it only when a plan trigger is present. |
| Review | Stop after writing spec.md, and after plan.md when required, so the user can review the artifact. |
| Operational follow-up | After review approval, default to committing reviewed task-local docs without a second approval question. Leaving them uncommitted requires explicit user approval plus reason and affected files. |
| Handoff | After docs and routine follow-up are ready, hand off to an execution skill such as task-execution-simple. |
After a review pause, treat any clear forward-motion message as approval to follow the recommended path. Ask a separate approval question only for hard gates.
More from adol1111/doc-driven-spec-workflow
doc-driven-spec-workflow
Use when a docs-driven repository request is unclear about whether the next step is scaffold initialization, clarification, roadmap decomposition, or current-task execution.
36milestone-planning
Use when a request or repository needs roadmap decomposition before spec writing because milestone boundaries, module grouping, or independently reviewable tasks are unclear.
35task-spec-execution
Use when older prompts, installed workflows, or tests still refer to task-spec-execution and need a compatibility redirect into the split task-preparation or task-execution-simple stages.
35docs-workflow-bootstrap
Use when initializing, bootstrapping, creating, or scaffolding the minimum docs-driven workflow layout for a repository before roadmap planning, specs, or implementation tasks exist.
33task-execution-simple
Use when task-local spec or plan work is complete and a concrete docs/tasks task should be implemented through the repository's simple direct execution path.
11doc-driven:task-spec-execution
Use when a docs-driven repository has a selected or selectable concrete docs/tasks task and needs task-local spec or implementation governance before code changes.
1