Task Generation

Task generation transforms a detailed implementation plan into organized, executable tasks grouped by user story priority (P1, P2, P3). It extracts acceptance criteria and maps them to models, services, endpoints, and tests across sequential phases, producing T-prefixed task items with parallelization markers for immediate developer use.

Test-first task organization prioritizes test-writing before implementation for each user story, ensuring every acceptance criterion has corresponding test coverage. This enforces TDD discipline and prevents incomplete feature delivery by making test tasks prerequisites in the task breakdown.

Yes. Task generation automatically invokes an audit command post-completion to validate constitutional compliance, requirement coverage, and task quality against governance rules. Critical issues block implementation progression until resolved.

Task generation requires a finalized implementation plan (plan.md) and specification document (spec.md) as mandatory prerequisites. Optional data model and contract files enable richer task mapping. These inputs are validated before task generation proceeds.

Tasks include parallelization markers ([P]) indicating which work can execute concurrently. Organization spans Phase 1 Setup, Phase 2 Foundational, Phase 3+ User Story Phases, and Phase Final Polish, enabling teams to identify independent work streams and accelerate delivery.

User-story organization groups related tasks by feature priority, enabling incremental user value delivery and progressive product rollout. This structure clarifies dependencies, improves sprint planning, and aligns implementation with business outcomes rather than isolated technical work.