Plaid
BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product.
Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents.
Install Build Mvp
$ npx skills add BuildGreatProducts/builder-os --skill build-mvp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuildGreatProducts/builder-os build-mvp --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BuildGreatProducts/builder-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/build-mvp .claude/skills/build-mvp && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "build-mvp" agent skill from https://github.com/BuildGreatProducts/builder-os/tree/main/skills/build-mvp into .claude/skills/build-mvp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-mvp", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BuildGreatProducts/builder-os/tree/main/skills/build-mvpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BuildGreatProducts/builder-os --skill build-mvp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuildGreatProducts/builder-os build-mvp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuildGreatProducts/builder-os.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/build-mvp .agents/skills/build-mvp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "build-mvp" agent skill from https://github.com/BuildGreatProducts/builder-os/tree/main/skills/build-mvp into .agents/skills/build-mvp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-mvp", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuildGreatProducts/builder-os --skill build-mvp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuildGreatProducts/builder-os build-mvp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuildGreatProducts/builder-os.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/build-mvp .cursor/skills/build-mvp && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "build-mvp" agent skill from https://github.com/BuildGreatProducts/builder-os/tree/main/skills/build-mvp into .cursor/skills/build-mvp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-mvp", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BuildGreatProducts/builder-os.git --path skills/build-mvp--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BuildGreatProducts/builder-os --skill build-mvp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuildGreatProducts/builder-os build-mvp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuildGreatProducts/builder-os.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/build-mvp .gemini/skills/build-mvp && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "build-mvp" agent skill from https://github.com/BuildGreatProducts/builder-os/tree/main/skills/build-mvp into .gemini/skills/build-mvp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-mvp", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BuildGreatProducts/builder-os build-mvpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BuildGreatProducts/builder-os --skill build-mvp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BuildGreatProducts/builder-os.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/build-mvp .github/skills/build-mvp && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "build-mvp" agent skill from https://github.com/BuildGreatProducts/builder-os/tree/main/skills/build-mvp into .github/skills/build-mvp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-mvp", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuildGreatProducts/builder-os --skill build-mvp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BuildGreatProducts/builder-os build-mvp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuildGreatProducts/builder-os.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/build-mvp .opencode/skills/build-mvp && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "build-mvp" agent skill from https://github.com/BuildGreatProducts/builder-os/tree/main/skills/build-mvp into .opencode/skills/build-mvp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-mvp", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
build-mvp- GitHub stars
- 228
- Token cost
- ~1.2k tokens
- SKILL.md length
- 593 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents.
- Works in 6 steps: Find the first unchecked task (- [ ]).… → Read what the task needs — its Files and… → Implement the task exactly as specified… → …
- Wants the full MVP built from their BuilderOS spec documents
- SKILL.md covers Setup, Work loop, Rules and Wrap up
- Calls git
What it does
Build Mvp is an agent skill from BuildGreatProducts/builder-os. 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…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Product roadmapping, Product strategy and PRD writing. It works with Git. The repository describes itself as: BuilderOS is your operating system for building with AI. The licence is MIT.
When your agent uses it
- Wants the full MVP built from their BuilderOS spec documents
- Phrases like build my MVP
- Execute the roadmap
- Start the build
Example prompts
- “build my MVP”
- “build the app”
- “execute the roadmap”
- “/build-mvp”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- 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…
- 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…
- 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…
What it can do on your machine
Read from SKILL.md and the folder at commit fb74cac. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Build Mvp loads about 1.2k tokens when it runs. Until then it costs about 196 tokens; SKILL.md has 593 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:42
the stack (dependencies, build output, `.env` files — never commit secrets), and commit everything with an initial comm
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from BuildGreatProducts/builder-os at commit fb74cac, republished under its MIT licence (© BuildGreatProducts). 593 words, ~1,164 tokens.
Download SKILL.mdSave it as
.claude/skills/build-mvp/SKILL.md (or your agent's skills folder).- name
- build-mvp
- description
- 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.
- license
- MIT
- metadata.author
- BuilderOS
- metadata.version
- 1.0
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.
Show full SKILL.md (298 more words)Show less
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.
© BuildGreatProducts, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/build-mvp of BuildGreatProducts/builder-os.
Open the folder on GitHubat commit fb74cac
Compare with similar skills
Build Mvp next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Build Mvp this skillBuildGreatProducts/builder-os | 228 | — | ~1.2k | Automated safety check: Notes | MIT | |
| PlaidBuildGreatProducts/plaid | 218 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Spec LiteChorus-AIDLC/Chorus | 1.2k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| Spec LiteChorus-AIDLC/Chorus | 1.2k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Spec LiteChorus-AIDLC/Chorus | 1.2k | — | ~2.4k | Automated safety check: Pass | AGPL-3.0 | |
| Spec LiteChorus-AIDLC/Chorus | 1.2k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Spec Lite
Chorus-AIDLC/Chorus
Lightweight, Chorus-native local specs for Chorus PM workflows in Hermes — a durable local spec .chorus/specs/<slug/spec.md (one per capability/feature) edited in place and NEVER synced (git history…
Spec Lite
Chorus-AIDLC/Chorus
Lightweight, Chorus-native local specs for Chorus PM workflows in Pi — a durable local spec .chorus/specs/<slug/spec.md (one per capability/feature) edited in place and NEVER synced (git history is…
Spec Lite
Chorus-AIDLC/Chorus
Lightweight, Chorus-native local specs for Chorus PM workflows on OpenClaw — a durable local spec .chorus/specs/<slug/spec.md (one per capability/feature) edited in place and NEVER synced (git…
Spec Lite
Chorus-AIDLC/Chorus
Lightweight, Chorus-native local specs for Chorus PM workflows — a durable local spec .chorus/specs/<slug/spec.md (one per capability/feature) edited in place and NEVER synced (git history is its…
Spec Lite Chorus
Chorus-AIDLC/Chorus
Lightweight, Chorus-native local specs for Chorus PM workflows on dsh — a durable local spec .chorus/specs/<slug/spec.md (one per capability/feature) edited in place and NEVER synced (git history is…
More from BuildGreatProducts/builder-os
All 8 skills in this repoDesign 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…
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.
Idea Validator
BuildGreatProducts/builder-os
Pressure-tests a product idea before the founder invests in planning, building, or launching.
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…
Build Loop Codex
BuildGreatProducts/builder-os
A skill your agent uses when building features with Codex (OpenAI Codex CLI) in any codebase and the work should go through a disciplined build → review → test → fix loop.
Build Loop Cursor
BuildGreatProducts/builder-os
A skill your agent uses when building features with Cursor in any codebase and the work should go through a disciplined build → review → test → fix loop.
Related
Works with
Categories
Questions about Build Mvp
What does Build Mvp do?
Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents. Build Mvp is an agent skill from BuildGreatProducts/builder-os. Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents.
When should I use Build Mvp?
Build Mvp fits situations like: wants the full MVP built from their BuilderOS spec documents; phrases like build my MVP; execute the roadmap; start the build.
How do I install Build Mvp in Claude Code?
Run `npx skills add BuildGreatProducts/builder-os --skill build-mvp -a claude-code`. Or copy the skill folder (skills/build-mvp in BuildGreatProducts/builder-os) into .claude/skills/build-mvp in your project. Claude Code loads it when a task matches its description.
How do I install Build Mvp in Codex?
Run `npx skills add BuildGreatProducts/builder-os --skill build-mvp -a codex`. Or copy the skill folder (skills/build-mvp in BuildGreatProducts/builder-os) into .agents/skills/build-mvp in your project. Codex loads it when a task matches its description.
Can I use Build Mvp in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BuildGreatProducts/builder-os --skill build-mvp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-mvp, .gemini/skills/build-mvp, .github/skills/build-mvp and .opencode/skills/build-mvp in your project.
What does Build Mvp need to run?
Going by SKILL.md and its folder, Build Mvp needs the command-line tools its instructions call (git).
Does Build Mvp access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Build Mvp safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Build Mvp use?
Build Mvp is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Build Mvp use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Build Mvp?
Skills that share tags, products or a category with Build Mvp: Plaid (BuildGreatProducts/plaid, 218 stars), Spec Lite (Chorus-AIDLC/Chorus, 1.2k stars), Spec Lite (Chorus-AIDLC/Chorus, 1.2k stars) and Spec Lite (Chorus-AIDLC/Chorus, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Build Mvp?
BuildGreatProducts (a GitHub user) maintains it in BuildGreatProducts/builder-os, which has 228 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on July 7, 2026.
Source: BuildGreatProducts/builder-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.