task-planner

You can break down a final specification into ordered vertical-slice task files stored under .ai/tasks/ by invoking the planner, which enforces self-contained boundaries and required frontmatter for auditable progress.

Vertical-slice task planning structures workflow by decomposing a specification into independent, testable end-to-end units. Each task is a complete unit stored as a file, allowing a reviewer to validate progress between execution phases.

To enforce human review between tasks during spec decomposition, the workflow applies a four-phase planning process with strict phase boundaries and guardrails, pausing for phase-by-phase audits before proceeding to the next task.

Yes, you can use this task planning workflow for minimal foundation development. It enforces minimal foundations within self-contained vertical slices, ensuring each task boundary remains explicit and testable without unnecessary overhead.

The best way to convert a final spec into vertical-slice tasks is to invoke the planner, which applies a four-phase workflow with phase-by-phase audits to generate ordered task files with explicit boundaries under .ai/tasks/.