requirement-sharpening
Requirement Sharpening
Use this skill to make requirements buildable and decidable, not merely well-formed. A requirement can be singular, ranked, and traceable — passing a structural audit — and still be impossible for a builder to implement unambiguously or for a tester to assert a definite outcome. This skill closes that gap: it converts "looks rigorous" into "a builder and a tester cannot misread it."
The governing rule: every requirement must name a definite, observable outcome and a way to decide whether that outcome was met. A requirement that hedges its own behavior, uses an unmeasurable quality word, or pins itself to today's file names fails this rule even when it is grammatically a single sentence.
This skill judges the content decidability of requirements — what each requirement actually commits to — not the document's outline or the standard's structural characteristics.
Scope
- Apply to: an individual requirement, a functional/non-functional requirement set, or a whole SRS that already has stable IDs and a structure — when the concern is "can someone build and verify this without guessing," not "is the document shaped to a standard."
- Use the six checks below in order; each has a detection cue, a pass/fail test, and the concrete rewrite.
- Preserve every stable ID and trace link exactly: sharpening edits the wording and thresholds of a requirement, never its ID.