What problem does it solve? Writing requirement specifications often produces vague, untestable statements, inconsistent IDs, and missing error paths. This Skill enforces a strict document structure and writing rules so every requirement is measurable, traceable, and ready for downstream backlog and test planning. ## Core Features & Use Cases - Structured spec template: Provides a mandatory section order covering business goals, actors, scope, business rules (BR), functional requirements (FR), non-functional requirements (NFR), glossary, assumptions, and open questions. - Testability enforcement: Bans vague words, requires numeric thresholds with measurement methods for all NFRs across 7 categories, and splits compound FRs into single-capability statements. - Decision and question management: Distinguishes blocking vs confirmatory open questions, pairs assumptions with impact statements, and mandates backlog updates plus decision logs after every spec change. - Use Case: When asked to write an SRS for a new feature, the Skill decides whether to create a new dated file or edit an existing one, drafts the spec from the template, then updates the product backlog and daily log in the same session. ## Quick Start Write a requirement specification for the online pre-order feature following the requirement-spec template and rules.
