Dependency specification
#[[file:../rules/review-base.md]] #[[file:../rules/git-workflow.md]] #[[file:../rules/project-structure.md]]
Purpose
Clarify requirement boundaries, ensure no ambiguity and no omissions, and provide reliable input for design.
Input
- Original description: text, prototypes, verbal descriptions provided by the requester, or conversation context
Steps
For each step, first output the title, then output the result
- Requirements organization: describe each requirement using Given/When/Then, check for gaps, contradictions, and missing branches
- Requirements confirmation: mark unclear or risky requirement points and confirm them one by one with the requester
- Scope definition: clarify the MVP scope and exclude what will not be done in this iteration
- Confirm requirements: in manual mode, output the requirements list and scope boundaries, and wait for developer confirmation before continuing
- Write to documents: each requirement or each category of requirements in a separate file, create an entry document referencing all requirement files (path follows
project-structuredocument storage specification) - Execute review: comply with
review-base, and only proceed to the next stage after passing
Output
- Requirements list: each item includes Given/When/Then
- Scope boundaries: what will be done in this iteration and what will not
Review checklist
- Given/When/Then: each requirement is complete, with no logical gaps
- No contradictions: no contradictory or conflicting requirements
- Boundary coverage: exception scenarios and boundary cases are covered
- Clear scope: MVP scope boundaries are clear
Stage end
Next stage:software-design
#[[file:../rules/stage-gate.md]]