discovery

Convert context reports and ambiguous product requests into testable specifications with Gherkin acceptance criteria.

8|Updated Jun 18, 2026

Search Tags:#requirements #discovery #product specification #milestone planning #gherkin #spec validation #context report

Ready to run

npx skills add https://github.com/ddobrin/plan-skills --skill discovery-ddobrin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discovery
Source: https://github.com/ddobrin/plan-skills/tree/main/plugins/orchestrator/skills/discovery
Command: npx skills add https://github.com/ddobrin/plan-skills --skill discovery-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovery converts an existing context report and an ambiguous product request into a rigorous, testable specification before planning or implementation begins.

Core Features & Use Cases

Context-driven specification: Uses research findings as the foundation for defining scope, requirements, constraints, and measurable outcomes.
Adversarial validation: Routes the specification through a spec-validator gate and requires confirmed findings to be resolved before advancement.
Use Case: When a research report exists but the desired feature remains underspecified, use Discovery to question assumptions, produce Gherkin acceptance criteria, and record a validated milestone specification.

Quick Start

Use the discovery skill with the existing context report to create and validate a testable specification for the requested milestone.

Frequently Asked Questions about discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I turn an ambiguous product request into a testable specification?▼

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.

How do I generate Gherkin acceptance criteria from a context report for milestone planning?▼

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.

What is adversarial spec validation and when do I need it for product specification?▼

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.

Do I need a context report before starting product discovery and requirements definition?▼

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.

Can I use spec validation for complex feature work and refactors that need product clarification?▼

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.