Epic Requirements Builder

To turn an epic into build-ready requirements, you select an epic from epic-list.md and the tool generates a comprehensive document with functional requirements, non-functional requirements, acceptance criteria, edge cases, and dependencies.

Structuring functional and non-functional requirements from an epic involves generating a standardized epic-NN-requirements.md file that separates FRs, NFRs, edge cases, and dependencies while adhering to upstream PRD and tech-stack constraints.

Preparing an epic requirements document for human or agent handoffs requires choosing an implementer mode at the start, which tailors a specific Phase 7 implementer-section in the final epic-NN-requirements.md output.

Yes, you need an upstream PRD and defined tech-stack constraints before generating epic requirements, as the tool follows these upstream constraints to accurately scope and draft the structured sections of the build-ready document.

Generating requirements is limited to epics already defined in epic-list.md, ensuring the output strictly follows the established scope and upstream PRD constraints rather than drafting arbitrary feature specifications.

Acceptance criteria and edge cases are important in an engineering handoff document because they reduce ambiguity between product and engineering teams by explicitly defining expected behaviors and handling of boundary conditions within the epic scope.