jon-devlapaz Requirements Auditor
Use this skill to find requirement defects before implementation turns them into bugs.
Workflow
- Classify each statement: goal, measurable objective, requirement, constraint, assumption, or implementation choice.
- Reject requirements that are compound, vague, unverifiable, ownerless, sourceless, or design-prescriptive without justification.
- Check each true requirement has one obligation, owner/approver, source, rationale, acceptance condition, and verification method.
- Check traceability to user intent, CONOPS, source material, repo constraints, or parent requirement.
- Identify contradictions, missing requirements, unstable assumptions, TBD/TBR values, and interface gaps.
- Separate must-fix findings from questions and acceptable residual risk.
- Output an audit report ordered by implementation risk: finding, affected requirement, evidence, impact, correction.
Source grounding
Start with references/source-grounding.md, then inspect Section 4.2 pages extraction/pages/page_067.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-quality claims.