What problem does it solve? It turns short, confirmed requirement statements into a structured, traceable requirements document (01-requirements.md) with numbered features, user stories, acceptance criteria, and constraints, so downstream design, testing, and development steps can reference stable IDs instead of ambiguous prose. ## Core Features & Use Cases - Structured Requirement Authoring: Expands raw input into F-XXX features, US-XXX user stories, and AC-XXX acceptance criteria with a traceability matrix and INVEST/GWT quality self-checks. - Multiple Intake Modes: Supports initial creation, incremental appends with continued numbering, background/context capture (--context), PRD package consumption (--from-prd), and design asset updates (--update-design). - Constraint & Compliance Capture: Records non-functional and release-compliance items as CON-XXX constraints with executable or manual verification methods, plus a needs-review block for open questions. - Use Case: After clarifying a login feature with stakeholders, run the skill to produce 01-requirements.md containing F-001 user registration, its user stories, quantified acceptance criteria, and a traceability matrix ready for system design. ## Quick Start Ask the agent to run /requirements and describe your confirmed feature needs so it generates the structured requirements document with numbered features, user stories, and acceptance criteria.
