What problem does it solve? Turning a vague product idea into a clear, testable specification is hard, and most users do not want to write or maintain a PRD themselves. This Skill owns that specification work: it converts natural-language intent into a defined outcome, scope boundaries, and observable acceptance criteria that development can act on. ## Core Features & Use Cases - Outcome Definition: Identifies the intended user, their problem, the action they take, and the observable result, resolving ordinary gaps with reversible defaults instead of endless questions. - Acceptance Criteria with Verification: Attaches an executable verification method to each acceptance criterion and carries previously accepted behavior forward through corrections and additions. - Semantic Integrity: Maintains canonical product terminology, records material changes to accepted rules, and prevents superseded documents from being treated as current requirements. - Use Case: You describe a new feature in plain language, such as adding offline mode to a note-taking app. The Skill produces a feature contract defining what is included, what is out of scope, and how each acceptance condition will be verified, without requiring you to write any specification document. ## Quick Start Ask the assistant to turn your feature idea into a working specification with acceptance criteria, for example: define the requirements and acceptance criteria for adding offline note syncing to my app.
