discovery

To convert an ambiguous product request into a testable specification, provide an existing context report to the discovery skill. It applies product-owner elicitation and adversarial spec validation to produce rigorous, testable requirements.

Generating Gherkin acceptance criteria from a context report involves questioning assumptions and defining scope based on research findings. The discovery process records a validated milestone specification by requiring confirmed findings to be resolved before advancement.

Adversarial spec validation is a gate that routes a product specification through a spec-validator to question assumptions and resolve confirmed findings. You need it for complex feature work, bug fixes, and refactors requiring product clarification before architectural planning.

Yes, you need a context report before starting product discovery. The discovery process uses an existing context report as the foundation for defining scope, constraints, and measurable outcomes before planning or implementation begins.

Yes, you can use spec validation for complex feature work, bug fixes, and refactors that require product clarification. It applies product-owner elicitation to question assumptions before architectural planning or implementation begins.