BuilderOS skill
Ten skills that take a product from idea to launch with an agent, passing work along through shared project documents
- 234 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Build MVP and Build Loop change project code and run tests, and Build MVP makes the first git commit at the end
- The skills read and write files in `docs`, and Launch Checklist reads the code, services and environment variables of the project
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/builderosDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Build MVP and Build Loop change project code and run tests, and Build MVP makes the first git commit at the end
- The skills read and write files in `docs`, and Launch Checklist reads the code, services and environment variables of the project
This is third-party code. Review the repository files before installing.
What it does
BuilderOS is a set of ten skills for product work with a coding agent. Each skill writes its result into the `docs` folder of the project, and the next one picks the document up without a retelling. Idea Generator gathers three to five directions and scores them on five axes. Idea Validator finds the core assumption, ranks fatal flaws, plans the first ten customers and gives a verdict: strong, weak or pivot. Product Planner runs an eight-section interview and writes `docs/product-vision.md`, `docs/prd.md` and `docs/product-roadmap.md` with task checkboxes. Design System turns screenshots, mockups and Figma links into `docs/design.md` with tokens and a `docs/design.html` page. Build MVP works through the roadmap task by task and makes the first git commit at the end. Three Build Loop variants (Claude Code, Codex, Cursor) run each step through build, review, test and fix. Design Better adds 50 interface heuristics, and Launch Checklist reads the project code to write a path from works on my machine to customers can use it.
Who it is for. Founders and solo developers who build a product with an agent and want documents, review and tests at every step instead of a pile of prompts.
Good fit when
- You have no idea yet but you do have experience or a business, and you need a few scored directions
- You have an idea and want to test its core assumption and plan the first ten customers before weeks of development
- The agent needs a spec and a roadmap in files so it can build by tasks and tick them off
- A mockup or screenshot is ready and has to become design tokens the agent implements
- The product is built and you want a step-by-step launch list: what you do, what the agent does, what you do together
Not a fit when
- A one-file task or a single edit: a chain of documents in `docs` only slows it down
- The project already runs on its own spec and roadmap in another format, and BuilderOS documents will drift from it
- The product is not software: the skills target app development and read code, stack and environment variables
Example request
plan my product: run the vision interview and save the documents in `docs`Limitations
The skill instructions are in English, and the documents in `docs` follow the language of the conversation until you ask otherwise. The skills write and read files in the `docs` folder at the project root, so run them from the repository root. Build MVP and Build Loop change code, and Build MVP also initializes git and makes the first commit, so use it in a new branch or an empty project. Build Loop ships in three variants for Claude Code, Codex and Cursor; other agents are left with Build MVP.
How to disable. Delete the skill folders (`idea-generator`, `product-planner`, `build-loop-claude-code` and the rest) from the project `.claude/skills/` or from your agent skills directory. The documents already created in `docs` stay in the project and are removed by hand.
FAQ
How do I install a single BuilderOS skill?
Give its path: `npx skills add BuildGreatProducts/builder-os/skills/design-system`. The `--skill` flag does the same, for example `npx skills add BuildGreatProducts/builder-os --skill product-planner`. Each skill is self-contained and works without the others.
Which of the three Build Loops should I take?
The one that matches your agent. `build-loop-claude-code` calls `/review` and `/security-review` for sensitive surfaces, `build-loop-codex` runs `/review` on uncommitted changes plus its own security pass, and `build-loop-cursor` uses the Cursor `/review`.
Do the skills have to run in order?
No, each works on its own. If an upstream document already exists, for example `docs/product-idea.md`, the next skill takes answers to its questions from it and asks less.
Which phrases trigger the skills?
The skills respond to plain requests in English: "help me find an idea", "validate my idea", "plan my product", "run the build loop", "design better". Each skill lists its own phrases in its description.
What format does Design System use for design tokens?
The open design.md format from Google: YAML tokens plus prose rationale any agent can implement from. A `docs/design.html` page for humans is created alongside, rendering the tokens and components live.
Discussion
No questions or reviews yet.
Related
SkillsSix linked skills take a project from a raw idea to a validated build plan and a first draft in Claude Code and Codex.
Six plugin packs with 44 skills covering idea, prototype, release with payments, fresh-reviewer checks and uptime monitoring.
Four Builder Methods skills: PRD with milestone prompts, skill builder, React and Tailwind design system, favicon set
Seven skills and a local CLI for game design: from idea to pitch and experiments, with decisions approved by a human
A 33-skill plugin with gates: question the request, verify facts against sources, test first, review by a second model
A hardware planning skill compares board architectures and components, then prepares a proposal and bill of materials
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| BuilderOS (this card) | no | 234 | |
| Superpowers | no | 316,679 | Superpowers sets discipline for development itself (plans, review, debugging), while BuilderOS adds the stages before code: idea, validation, spec, design system and launch. |
| BMad Method | no | 55,338 | BMad Method hands roles to agents inside one process, while BuilderOS is built from self-contained skills that exchange documents in docs. |
README in short
The README explains why an agent needs discipline: speed without a plan yields features that only compile. It then gives skill tables by stage, a diagram of document exchange through `docs` and install routes through the skills CLI. The repository is the successor of the PLAID project.
README badge
Original SKILL.md
--- name: product-planner description: | 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. license: MIT metadata: author: BuilderOS version: "1.0" compatibility: Requires file system access to write the docs/ directory. --- # Product Planner — Vision Intake + Document Generation This skill captures a founder's product vision through a structured intake conversation and then generates three product documents that downstream skills (Launch Checklist, the Build Loop skills) and coding agents consume. ## Shared Context You are a product development advisor. You are warm, direct, and opinionated. You treat the founder as capable and smart — you're here to help them articulate what's already in their head, not to lecture them. **Validation rule:** Before generating any documents from `docs/VISION.md`, validate it against the template in [resources/VISION-TEMPLATE.md](./resources/VISION-TEMPLATE.md) — all sections present in order, every field filled, enum values valid, list fields non-empty. If validation fails, report the problems and fix them in `docs/VISION.md` before proceeding. **Resumability:** This skill is designed to be interrupted and resumed. Always check the current project state before starting work — does `docs/VISION.md` exist? Are docs present? Pick up from where things left off rather than restarting. ## Modes The Product Planner has two modes. Pick the right one based on context: