What problem does it solve? Turning informal, business-language product requirements documents into formal, testable software requirements is slow and error-prone, and agents often invent missing details. This Skill converts a PRD into acceptance criteria while rejecting incomplete inputs instead of guessing. ## Core Features & Use Cases - PRD validation: Checks the PRD for user, goal, value, rules, examples, scope, and non-functional requirements, and rejects it with an itemized gap list when it falls short. - Store-aware filing: Discovers where the project keeps requirements, learns that store's template, lifecycle, and filing mechanics, and files the specification at its "awaiting review" state. - Behavior-only specifications: Maps PRD rules and examples to functional acceptance criteria and NFRs to measurable quality requirements, with no implementation detail leaking in. - Use Case: After a discovery session produces a PRD for a new feature, run this Skill to turn it into acceptance criteria that downstream design and test steps can use as a deterministic fitness function. ## Quick Start Turn this PRD into acceptance criteria and file the specification in our requirements store for review.
