create-tasks

To decompose accepted user stories into implementation tasks, you can use deterministic decomposition heuristics that generate codebase-agnostic tasks with contract and testable definitions of done. This produces one task per acceptance criterion, ensuring safe consumption by an AI coding agent.

Task decomposition with NFR threshold verification is the process of generating implementation tasks that specifically validate measurable performance, security, and reliability thresholds defined in the Software Requirements Specification. It creates dedicated tasks to ensure these non-functional requirements are tested.

You maintain traceability between implementation tasks and linked test cases by generating task indices and coverage matrices that seed Definition of Done lines referencing those linked test cases. This ensures every implementation task has auditable connections back to requirements.

You prevent codebase leakage by running a boundary audit validation that flags generated tasks containing framework names, file paths, code fences, or code-like handler prescriptions. Instead of auto-rewriting these specifics, it records Open Questions for human review.

Yes, task decomposition supports cross-cutting non-functional requirements by minting a single shared task for NFRs referenced by multiple user stories. This cross-cutting task is then linked to every serving story to avoid duplication and ensure comprehensive coverage.

Yes, you need an Accepted Software Requirements Specification and at least one Accepted User Story under an Accepted Epic before decomposing requirements into tasks. The process operates strictly on these accepted artifacts to ensure valid implementation task generation.