cmd-product-scope-review

To clarify your MVP scope before design, evaluate product scope decisions using four modes (EXPAND, SELECTIVE EXPAND, HOLD, REDUCE) to surface assumptions, risks, and trade-offs. This structured method outputs a mode-specific scope representation and clear next steps.

Evaluating product scope is best handled by applying mode-driven analysis to feature requests, which surfaces project constraints and strategic trade-offs. This approach generates a recommended mode, key assumptions, and actionable next steps to align scope with intent.

Surface assumptions and risks during early-stage brainstorming by applying structured scope analysis modes to your topic. This process grounds decisions by detecting project type and reviewing recent history to output mode-specific risks and recommended next steps.

You need to reduce product scope when constraints outweigh resources, and selectively expand when targeted additions drive strategic value. Applying the four scope evaluation modes clarifies these trade-offs and outputs a recommended mode for your MVP delineation.

Yes, you can use scope review for early-stage ideas without existing specs. The process detects project type, reviews recent history, and applies the four modes to generate a mode-specific scope plan, key assumptions, and next steps from scratch.

Product scope misaligns with strategic intent when assumptions and trade-offs are not surfaced pre-design. Applying a structured four-mode scope evaluation clarifies what to build, ensuring your MVP delineation matches your project's strategic goals.