mvp

Plan MVPs from problem briefs to MVP_SCOPE and ROADMAP artifacts.

5|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Nathan13888/nice-skills --skill mvp-nathan13888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mvp
Source: https://github.com/Nathan13888/nice-skills/tree/main/skills/mvp
Command: npx skills add https://github.com/Nathan13888/nice-skills --skill mvp-nathan13888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The MVP Product Planner helps teams map vague product ideas into a concrete, actionable MVP strategy by guiding deep requirements gathering, feature ideation, architecture decisions, and living documentation.

Core Features & Use Cases

  • Deep requirements gathering to anchor problem space and seed questions.
  • Structured artifacts generation: OVERVIEW, FEATURES, MVP_SCOPE, ROADMAP, and DELIVERABLES.
  • Plan-mode discipline and prompts to drive deliberate thinking before writing any artifacts.

Quick Start

Provide a seed product description or prompt for onboarding to begin the Plan Mode workflow.

Frequently Asked Questions about mvp

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

FAQPage Schema
How do I define the scope for an MVP from a vague product idea?

An MVP roadmap is created by guiding users through problem briefs to formal deliverables, producing structured artifacts like OVERVIEW, FEATURES, MVP_SCOPE, and ROADMAP to ensure deliberate thinking before documentation.

What is the best way to document architecture decisions during product planning?

The best way to document architecture decisions during product planning is through structured artifacts and formal handoff deliverables, using plan-mode discipline to drive deliberate thinking before writing any files.

Can I use this MVP planner if I only have a brief problem description?

Yes, you can use the MVP planner with a brief problem description. You provide a seed product description or prompt for onboarding to begin the plan-mode workflow and deep requirements gathering.

What deliverables should I expect from structured MVP feature ideation?

From structured MVP feature ideation, you should expect formal artifacts including OVERVIEW, FEATURES, MVP_SCOPE, ROADMAP, and DELIVERABLES, ensuring your product strategy is mapped into concrete, actionable outputs.

Why does MVP planning require a plan-mode workflow before writing files?

MVP planning requires a plan-mode workflow to enforce deliberate thinking and deep requirements gathering before writing any artifacts, ensuring that architecture decisions and feature ideation are fully scoped and validated.