wa:spec-discovery

To discover feature requirements collaboratively, this Skill guides a multi-stage workflow exploring problem, users, behavior, data, priorities, and integration domains. It tracks completeness interactively and outputs a structured DISCOVERY.md document.

Domain-based requirements discovery is an early-stage spec generation process that explores problem space, users, functional behavior, and data to confirm assumptions. You need it when teams must capture decisions and determine domain coverage before writing testable acceptance criteria.

To generate a discovery document, run the Skill with a feature description. It performs codebase research, ingests FRDs, and writes a structured DISCOVERY.md file to docs/{feature}/ containing requirements, acceptance criteria candidates, and open questions.

Yes, this workflow applies to early-stage spec generation where teams must confirm assumptions and capture decisions. It requires plan-mode activation and performs codebase research to satisfy statusline stage updates during the discovery process.

The best way to track completeness is using a gated coverage workflow that applies prompts tailored to each domain's goals. This ensures requirements discovery captures problem space, users, behavior, data, priorities, and security dimensions before generating spec documentation.