contract-first-mvp-planning

Sequence MVP development from existing API contracts and schema.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ivegamsft/work-tracker --skill contract-first-mvp-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-first-mvp-planning
Source: https://github.com/ivegamsft/work-tracker/tree/main/.squad/skills/contract-first-mvp-planning
Command: npx skills add https://github.com/ivegamsft/work-tracker --skill contract-first-mvp-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams plan and execute an MVP by leveraging existing API contracts and schema, avoiding the pitfalls of stubbed services and enabling rapid progression based on real, validated work.

Core Features & Use Cases

  • Contract-Based Planning: Sequences MVP development from the existing contracts and schema, not from stubbed services.
  • Risk Prioritization: Identifies and prioritizes the first MVP loop by implementation risk.
  • Modular Development: Encourages the development of enabling and operational modules in parallel.

Quick Start

To initiate the MVP planning for your project, execute the 'plan_mvp' script from the 'scripts/' directory.

Frequently Asked Questions about contract-first-mvp-planning

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

FAQPage Schema
How do I plan MVP development using existing API contracts and schema?

MVP planning with API contracts sequences development based on existing routers, validators, and DTOs rather than stubbed services. It identifies implementation risks and prioritizes features mapping directly to the schema for rapid progression.

What is schema-driven MVP planning and when do I need it?

Schema-driven MVP planning sequences development from existing API contracts to avoid stubbed service pitfalls. It is needed when architecture teams require validated work progression and parallel development of enabling and operational modules.

Do I need defined routers and DTOs to use contract-first MVP planning?

Contract-first MVP planning requires a codebase with defined routers, validators, DTOs, and schema. These existing API contracts form the foundation for sequencing development and identifying implementation risks.

What's the best way to prioritize MVP features by implementation risk?

Prioritizing MVP features by implementation risk involves identifying the first development loop from existing API contracts. Contract-based planning sequences features with direct schema mappings and encourages parallel modular development.

How to start MVP planning from existing API contracts?

Starting MVP planning from API contracts involves executing the plan_mvp script from the scripts directory. This sequences development based on existing schema, identifies risks, and prioritizes features with direct schema mappings.

Why does contract-first MVP planning avoid stubbed services?

Contract-first MVP planning avoids stubbed services to enable rapid progression based on real, validated work. By leveraging existing API contracts and schema, teams develop enabling and operational modules in parallel while prioritizing implementation risks.