Requirements Distiller

Requirements Distiller

Use this skill to turn messy intent into testable obligations without smuggling in design.

Workflow

1. Classify input into: broad goals, measurable objectives, requirements, constraints, assumptions, implementation choices, and open questions.
2. Do not convert goals or objectives into requirements until the obligation is specific, necessary, and testable.
3. Write each requirement as one obligation with stable subject, required behavior, boundary/condition, and acceptance signal.
4. Keep implementation choices deferred unless the user or source makes them constraints.
5. Add owner/approver, trace source, rationale, acceptance criteria, verification method, and evidence artifact for each requirement.
6. Mark assumptions with confirmation path and deadline when they affect scope or acceptance.
7. Output a requirements matrix plus a deferred-design list and open-question list.
8. Send high-risk or ambiguous requirements to requirements-auditor before coding.

Source grounding

Start with references/source-grounding.md, then inspect Section 4.2 pages extraction/pages/page_064.md through extraction/pages/page_068.md and Appendix C pages extraction/pages/page_207.md through extraction/pages/page_209.md before making requirement-writing claims.