aped-analyze

To create a validated MVP scope from a vague idea, you need guided discovery and parallel research to synthesize vision, users, and constraints into a structured product brief. This approach enforces validation gates to ensure evidence-backed outputs before proceeding.

Parallel research for product briefs dispatches multiple agents concurrently to investigate business, domain, and technical constraints. By analyzing these perspectives simultaneously, it reduces blind spots and synthesizes evidence-backed findings before drafting your MVP scope.

Yes, guided discovery applies to both greenfield and brownfield Claude Code projects to define constraints. It runs activation guards and collects user validation across four rounds to ensure the discovery summary accurately reflects project limits before research proceeds.

Generating a product brief requires answering guided discovery questions, approving the summary, and dispatching parallel research agents. After agents complete research, you synthesize the brief from a template, run placeholder linting, and update the pipeline state upon explicit approval.

The best way to structure a product brief before a PRD is using a template that synthesizes evidence from parallel research. This method validates outputs through placeholder linting and brief checks, ensuring your vision and MVP scope are fully validated before the next phase.

User gates are required before dispatching research to ensure the discovery summary is explicitly approved. Enforcing these gates prevents unvalidated assumptions from entering the research phase, ensuring the final product brief is evidence-backed and accurately scoped.