af-discovery-process

Product discovery requires structured requirements gathering to map ideas to actionable plans. You can use a 4-question interview framework to elicit essential project information, define user personas, and document architectural decisions before development begins.

Documenting architectural decisions during project planning involves generating specific artifacts like ADRs and Tech Stack Agreements. A structured discovery process creates these comprehensive documentation outputs alongside project overviews and user analyses to ensure technical constraints are understood.

Yes, structured product discovery supports integration with work management tools like Linear. After gathering requirements and generating project documentation, you can use this integration directly for feature creation and tracking within your development workflow.

To start a discovery session for mapping product ideas to actionable plans, initiate the process by running the 'start-specs' command with your project name. This triggers the structured 4-question interview framework to begin gathering essential context.

A structured product discovery process generates comprehensive documentation artifacts including project overviews, user analyses, entity models, Architecture Decision Records (ADRs), and tech stack agreements to thoroughly document business drivers and technical constraints.