solution-scoping_skill

Overview

This skill helps teams decide what to build first by forcing concrete feature prioritization and defining a tight MVP boundary. It translates problem framing and user models into a ranked feature list, explicit cuts, and a clear scope that feeds product requirements. Use it when the problem is validated and you need to minimize risk and time-to-learn.

How this skill works

Ingests problem-framing artifacts and user-model outputs, or accepts a raw feature list. It generates an exhaustive feature inventory, applies prioritization frameworks (Impact vs Effort, MoSCoW, user-value filters), and draws a hard MVP line with rationale. Outputs include prioritized features, an MVP definition, deferred items, and risks from each cut.

When to use it

• After user research validates the core problem but before engineering work begins
• When stakeholders disagree on what belongs in the first release
• To convert personas and JTBD into a testable, minimal product
• When you need a defensible list of features for a PRD or roadmap
• If you want to reduce scope creep and focus on the smallest testable bet

Best practices

• Start with an exhaustive list, then be ruthless about cuts
• Use at least two prioritization lenses (impact/effort + user value)
• Define the MVP as the smallest thing that validates the core assumption
• Treat cuts as "not yet" and document the rationale and dependencies
• Validate every cut against the core user goal and measurable outcomes

Example use cases

• A startup with validated demand deciding which features to build for launch
• A product manager reconciling competing stakeholder requests into an MVP
• A design team translating personas and scenarios into a prioritized feature set
• A cross-functional team preparing a scoped PRD and roadmap for the next quarter
• A founder needing a defensible scope to pitch development timeline and budget