build-mvp
Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents. Triggers on phrases like "build my MVP", "build the app", "execute the roadmap", "start the build", "work through the whole roadmap", "build everything", or any request to implement the entire plan rather than a single task or phase. Requires docs/prd.md and docs/product-roadmap.md (plus docs/product-vision.md and docs/design.md for context). Works through every roadmap task in order — implementing, testing, and verifying each before moving on, marking checkboxes and updating the status line — and runs until all tasks are complete and the magic moment works end to end, then initializes git with an initial commit and offers to connect a remote repo.
- Installs
- 1.6K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/buildgreatproducts/builder-os --skill build-mvp- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads build-mvp automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Build MVP
Build the complete app by executing every task in docs/product-roadmap.md, in order, until all tasks are checked off.
Setup
Read docs/product-roadmap.md first — it is the source of truth for what to build and in what order. docs/prd.md is the technical spec behind it; docs/design.md holds the visual design tokens; docs/product-vision.md holds the product strategy. Do not load these documents wholesale — each phase lists the specific Reference sections to read, plus whatever a task's Notes line points to. If docs/product-roadmap.md or docs/prd.md is missing, stop and tell the user to run the Product Planner skill first (part of BuilderOS: https://github.com/BuildGreatProducts/builder-os).
Work loop
Repeat until every task in the roadmap is complete:
- Find the first unchecked task (
- [ ]). Tasks are ordered intentionally — never skip ahead. - Read what the task needs — its Files and Notes lines, plus the current phase's Reference sections if not yet read this session.
- Implement the task exactly as specified — file paths, package names, and config values are deliberate. Follow the repo's
CLAUDE.md/AGENTS.mdguidelines: simplest implementation that satisfies the task, no speculative features, surgical changes only. - Test and verify before moving on. Run the verification step at the end of the task's Notes, run the app, run existing tests, and add tests for new logic. If verification fails, fix it first — never mark a failing task complete or start the next task with the app broken.
- Mark the task complete — change
- [ ]to- [x]and update the header status line (**Status:** X/Y tasks complete,**Current Phase:** ...). - At each phase boundary: run the app end to end and confirm the phase's Goal is true and demoable before starting the next phase. No git or GitHub actions here — version control happens once at the end, after every phase is complete.
Rules
- The PRD's stack choices are final — implement them, never substitute alternatives.
- Visual styling comes from
docs/design.mdtokens — never invent colors, type, or spacing. Ifdocs/design.mddoesn't exist, follow the roadmap's foundation-phase guidance: prompt the user to run the Design System skill before styling work begins. - If a task is ambiguous or conflicts with the PRD, check the PRD section it references; if still unclear, ask one specific question rather than guessing.
- If necessary work isn't covered by any task, surface it and propose adding a task — don't silently expand scope.
- Keep going until
**Status:** Y/Y tasks complete: every task checked, every phase verified, the magic moment working end to end. - No git or GitHub actions (init, commits, branches, pushes, PRs) until every phase is complete — version control is the wrap-up step, not part of the work loop.
Wrap up
When every task is checked off and the magic moment has been verified end to end:
- Initialize git and create the initial commit. If the project isn't a git repository yet, run
git init, add a sensible.gitignorefor the stack (dependencies, build output,.envfiles — never commit secrets), and commit everything with an initial commit message naming the product and noting the MVP build is complete. If the project is already a git repository, commit the build on the current branch instead. - Ask the user if they want to connect a remote repo. Don't create or push anything on your own — ask: "Want me to connect this to a remote repo? I can create one on GitHub (public or private) or connect an existing URL." If yes, set it up as
origin, push, and confirm the push succeeded. If no, leave it local and tell them the commit is ready to push whenever they are.
FAQ
What does the build-mvp skill do?
Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents. Triggers on phrases like "build my MVP", "build the app", "execute the roadmap", "start the build", "work through the whole roadmap", "build everything", or any request to implement the entire plan rather than a single task or phase. Requires docs/prd.md and docs/product-roadmap.md (plus docs/product-vision.md and docs/design.md for context). Works through every roadmap task in order — implementing, testing, and verifying each before moving on, marking checkboxes and updating the status line — and runs until all tasks are complete and the magic moment works end to end, then initializes git with an initial commit and offers to connect a remote repo.
How do I install build-mvp?
Run npx skills add https://github.com/buildgreatproducts/builder-os --skill build-mvp in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/build-mvp/ (personal) or .claude/skills/build-mvp/ (project).
Which AI agents can use build-mvp?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is build-mvp safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains build-mvp?
It is published by buildgreatproducts in buildgreatproducts/builder-os. It has 1,632 recorded installs.
More from buildgreatproducts/builder-os
design-system
buildgreatproducts/builder-os
Translates an image (or a set of image references — screenshots, mockups, Figma URLs, live websites) into two mirrored design-system artifacts: docs/design.md (YAML tokens + prose, following Google's open design.md format, for the coding agent) and docs/design.html (a self-contained, token-driven style guide rendering every token and component live, for the human to read). Reads the imagery, asks targeted clarifying questions, derives the design tokens (colors, typography, spacing, rounded, components), and writes both files. Fully standalone — requires no other document or skill. Use when the founder says "create a design system", "design from image", "translate image to design", "create design.md", "image to design system", "extract design tokens", or shares an image with no other clear intent.
product-planner
buildgreatproducts/builder-os
Vision intake conversation followed by generation of three product documents — docs/product-vision.md (strategy and brand), docs/prd.md (technical spec for coding agents), and docs/product-roadmap.md (phased build plan with task checkboxes). Also captures the founder's answers as docs/VISION.md. Use when the founder says "plan my product", "plan a product", "define my vision", "generate a PRD", "create a roadmap", "spec out my idea", "help me build something", or wants to convert an idea into shippable spec documents.
idea-validator
buildgreatproducts/builder-os
Pressure-tests a product idea before the founder invests in planning, building, or launching. Surfaces fatal flaws, tests whether the problem is real, maps real competition (including current behavior), plans first 10 customers, defines a 2-week MVP test, returns a strong/weak/pivot verdict, then sharpens docs/product-idea.md based on the founder's direction calls. Use when the founder says "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "stress test my idea", or otherwise wants to evaluate an idea before committing.
launch-checklist
buildgreatproducts/builder-os
Use when the user's product is built (or nearly built) and they want to get it live and accessible to customers. Triggers on phrases like "create my launch checklist", "how do I deploy this", "help me launch", "get this live", "put this in production", "ship it to customers", "what do I need to do to go live", or any request for a step-by-step path from working code to a product customers can use. Audits the current codebase — stack, services, environment variables, payments, deploy config — then writes a plain-English, step-by-step launch guide to docs/launch-checklist.md. Every step is marked as something the user must do themselves, something their coding agent can do, or both together, and all technical terms are explained for non-technical founders.
idea-generator
buildgreatproducts/builder-os
Guided discovery of a product idea by mining what the founder already knows or already does — covers source selection (business vs. expertise), context capture, pattern synthesis, candidate scorecard, and writes docs/product-idea.md. Use when the founder says "generate an idea", "help me find an idea", "what should I build", "product idea from my business", "product idea from my expertise", or otherwise needs to discover a product concept worth building.
build-loop-claude-code
buildgreatproducts/builder-os
Use when building features with Claude Code in any codebase and the work should go through a disciplined build → review → test → fix loop. Triggers on "run the build loop", "build the next task", "continue the plan", "build this feature properly", or any request to implement work from a plan file or a direct feature prompt. Builds from the plan (or the prompt if no plan exists), runs Claude Code's /review (plus /security-review for sensitive surfaces) and fixes every issue found, tests and verifies the feature end to end, fixes anything testing surfaces, and reports back once complete. Repeats until all plan tasks are checked off.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.