project-discovery

To capture project requirements before writing documentation, run a structured discovery conversation that guides discussions on goals, stakeholders, features, and constraints, then compiles responses into a finalized DISCOVERY.md file.

Project discovery for stakeholders should include structured discussions on goals, stakeholders, constraints, tech preferences, and success metrics to produce a standardized DISCOVERY.md with Project Overview, Requirements, Tech Stack, Complexity, and Phases.

You generate a DISCOVERY.md from consultation responses by initiating a discovery session with /init --full, which triggers a rules-based workflow that compiles your answers into the finalized markdown document.

Yes, you can use this discovery workflow for any project type because it applies across various projects, guiding structured discussions to identify requirements, complexity, and phases regardless of the specific domain.

The best way to start a requirements discovery session is to begin with /init --full, which engages guided conversations to accurately clarify project goals and constraints before generating the final DISCOVERY.md.

Yes, the generated DISCOVERY.md integrates with the dev-docs-writer pipeline, allowing downstream documentation generation to use the captured project overview, requirements, and tech stack details.