recommend-mvp

Author MVP recommendation artifacts selecting v1 use cases and deferring others.

3|Updated Jan 25, 2026

Search Tags:#mvp #risk management #product planning #intent-driven development #scope narrowing #specify pipeline

Ready to run

npx skills add https://github.com/kapilvirenahuja/garura --skill recommend-mvp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recommend-mvp
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/recommend-mvp
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill recommend-mvp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces an MVP recommendation that prevents the specify pipeline from turning every named use case into an oversized, bloated v1 scope that the team cannot ship.

Core Features & Use Cases

MVP scope narrowing artifact: Writes an MVP recommendation at .garura/product/scope/mvp-recommendation.md that selects primary use cases for v1 and defers the rest to v1.1+.
Traceable recommendations: Forces every narrowing decision to trace back to the project brief use cases and constraints, using a schema-anchored output structure.
Risk- and envelope-aware: Incorporates market brief risks and project profile envelope dimensions (team_size, delivery_ambition, timeline, budget_sensitivity) to justify deferrals and success criteria.
User-grounded ambiguity handling: Detects ambiguous narrowing scenarios and appends user grounding questions instead of inventing classifications.

Quick Start

Ask the product-keeper to run recommend-mvp to generate the MVP recommendation file at the configured output path for the current specify Stage 2.75 inputs.

Frequently Asked Questions about recommend-mvp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I narrow MVP scope to prevent shipping an oversized v1?▼

MVP scope narrowing requires authoring a decision artifact that selects primary use cases for v1 and defers the rest to v1.1+. This prevents bloated v1 scope by enforcing traceable decisions based on project brief constraints and user grounding answers.

What is intent-driven development for product planning?▼

Intent-driven development for product planning uses a specify pipeline to sequence domain selection and capability configuration. It grounds scope narrowing decisions in market brief risks and project profile envelopes like team size, delivery ambition, and budget sensitivity.

How do I manage risk when deferring use cases to v1.1+?▼

Managing risk when deferring use cases to v1.1+ involves incorporating market brief risks and project profile envelope dimensions. This risk-aware approach justifies deferrals and success criteria by tracing every narrowing decision back to original project constraints.

Can I automate scope narrowing with ambiguous product brief inputs?▼

With ambiguous product brief inputs, scope narrowing cannot be fully automated; the process detects ambiguous scenarios and appends user grounding questions instead of inventing classifications. This ensures MVP decisions remain traceable to actual project constraints.

What is the best way to structure an MVP decision artifact?▼

The best way to structure an MVP decision artifact is using a schema-anchored output format that enforces traceable recommendations. This structure forces every v1 scope decision to trace back to project brief use cases while incorporating risk and envelope dimensions.