cpm:discover

You can write a problem brief by running a guided discovery workflow that asks phase-by-phase questions to define motive, audience, current state, success criteria, and constraints, generating a formal document for stakeholder alignment.

Guided problem discovery is a phase-based questioning process that helps you understand a problem before jumping to solutions. You need it for project scoping to ensure deliberate exploration and decision points before committing to a plan.

Start a phase-by-phase discovery session by invoking the discovery workflow command to initiate guided questioning. The workflow creates a persistent progress file to track your state and supports seamless resumption across sessions.

Yes, you can resume an interrupted product discovery session because the workflow creates and updates a persistent .cpm-progress.md state file. This file supports seamless resumption of the gated phase-by-phase questioning process.

Yes, the problem discovery workflow generates a final plan document suitable for stakeholder alignment. It compiles your answers from the gated questioning phases into a formal problem brief for planning and scoping.

The best way to define success criteria and constraints is using a structured problem discovery workflow that guides you through gated phases, ensuring deliberate exploration of your motive and current state before generating a formal brief.