skills/buildgreatproducts__builder-os
1
0
Fork 0
mirror of https://github.com/BuildGreatProducts/builder-os.git synced 2026-09-19 06:02:32 +08:00
Code Issues Packages Projects Releases Wiki Activity

Point repo references at builder-os, add formerly-PLAID note

Browse Source 
- All install commands and cross-skill links updated from
  BuildGreatProducts/BuilderOS to BuildGreatProducts/builder-os
- README opens with a note that BuilderOS is the successor to PLAID,
  linking to the original repo

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Chris Ashby
2026-06-11 13:55:10 +01:00
parent d5e9379565
commit 44579a1546
7 changed files with 20 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+1 -1
View File
@@ -15,7 +15,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
## [0.4.0] - 2026-06-11
### Added
- **`npx skills add` installation** via the [skills CLI](https://github.com/vercel-labs/skills): install everything with `npx skills add BuildGreatProducts/BuilderOS`, a single skill by path (`.../skills/product-planner`) or by name (`--skill product-planner`). README gained a full Installation section
- **`npx skills add` installation** via the [skills CLI](https://github.com/vercel-labs/skills): install everything with `npx skills add BuildGreatProducts/builder-os`, a single skill by path (`.../skills/product-planner`) or by name (`--skill product-planner`). README gained a full Installation section
- MIT `LICENSE.txt` at the repo root
### Changed
README.md
+13 -11
View File
@@ -1,5 +1,7 @@
# BuilderOS
> **Formerly PLAID.** BuilderOS is the successor to [PLAID — Product Led AI Development](https://github.com/BuildGreatProducts/plaid). The PLAID skills have been refactored into standalone BuilderOS skills; new development happens here.
**An operating system for builders.** BuilderOS is a collection of agent skills that give product builders a repeatable system for ideating, designing, and building software products with AI — turning coding agents from autocomplete into disciplined collaborators that ship reviewed, tested work.
## Why
@@ -84,7 +86,7 @@ BuilderOS uses the [skills CLI](https://github.com/vercel-labs/skills). Run thes
### Everything in one go
```sh
npx skills add BuildGreatProducts/BuilderOS
npx skills add BuildGreatProducts/builder-os
```
Installs every BuilderOS skill at once. Use this if you want the full ideate → plan → design → build → launch pipeline.
@@ -92,15 +94,15 @@ Installs every BuilderOS skill at once. Use this if you want the full ideate →
### Individual skills
```sh
npx skills add BuildGreatProducts/BuilderOS/skills/idea-generator
npx skills add BuildGreatProducts/BuilderOS/skills/idea-validator
npx skills add BuildGreatProducts/BuilderOS/skills/product-planner
npx skills add BuildGreatProducts/BuilderOS/skills/design-system
npx skills add BuildGreatProducts/BuilderOS/skills/build-mvp
npx skills add BuildGreatProducts/BuilderOS/skills/build-loop-claude-code
npx skills add BuildGreatProducts/BuilderOS/skills/build-loop-codex
npx skills add BuildGreatProducts/BuilderOS/skills/build-loop-cursor
npx skills add BuildGreatProducts/BuilderOS/skills/launch-checklist
npx skills add BuildGreatProducts/builder-os/skills/idea-generator
npx skills add BuildGreatProducts/builder-os/skills/idea-validator
npx skills add BuildGreatProducts/builder-os/skills/product-planner
npx skills add BuildGreatProducts/builder-os/skills/design-system
npx skills add BuildGreatProducts/builder-os/skills/build-mvp
npx skills add BuildGreatProducts/builder-os/skills/build-loop-claude-code
npx skills add BuildGreatProducts/builder-os/skills/build-loop-codex
npx skills add BuildGreatProducts/builder-os/skills/build-loop-cursor
npx skills add BuildGreatProducts/builder-os/skills/launch-checklist
```
Every skill is fully self-contained — install just the Design System to turn a screenshot into design tokens, or just a Build Loop to execute a roadmap someone else wrote. You only need the Build Loop for the coding agent you actually use.
@@ -108,7 +110,7 @@ Every skill is fully self-contained — install just the Design System to turn a
### By skill name
```sh
npx skills add BuildGreatProducts/BuilderOS --skill product-planner
npx skills add BuildGreatProducts/builder-os --skill product-planner
```
### Manual installation
skills/build-mvp/SKILL.md
+1 -1
View File
@@ -13,7 +13,7 @@ Build the complete app by executing every task in `docs/product-roadmap.md`, in
## 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/BuilderOS).
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
skills/design-system/SKILL.md
+1 -1
View File
@@ -252,7 +252,7 @@ Then suggest the natural next step based on project state:
- If `docs/product-vision.md` exists but `docs/prd.md` does not → "Run the **Product Planner** skill to generate the PRD — it'll consume these tokens directly."
- If neither exists → "Run the **Product Planner** skill if you want to wrap this design into a full product vision and PRD."
If the Product Planner skill isn't installed, mention that it's part of BuilderOS: https://github.com/BuildGreatProducts/BuilderOS.
If the Product Planner skill isn't installed, mention that it's part of BuilderOS: https://github.com/BuildGreatProducts/builder-os.
-----
skills/idea-generator/SKILL.md
+1 -1
View File
@@ -222,7 +222,7 @@ After writing `docs/product-idea.md`, say:
If the Idea Validator or Product Planner skill is not installed, append:
> "Both skills are part of BuilderOS: https://github.com/BuildGreatProducts/BuilderOS"
> "Both skills are part of BuilderOS: https://github.com/BuildGreatProducts/builder-os"
If the founder wants to continue immediately and the relevant skill is installed, hand off — the receiving skill will use `docs/product-idea.md` as pre-filled context.
skills/idea-validator/SKILL.md
+1 -1
View File
@@ -306,7 +306,7 @@ After writing the report and applying edits, route based on verdict:
If the Product Planner or Idea Generator skill isn't installed and you reference it, append:
> "Both skills are part of BuilderOS: https://github.com/BuildGreatProducts/BuilderOS"
> "Both skills are part of BuilderOS: https://github.com/BuildGreatProducts/builder-os"
If the founder wants to continue to planning immediately and the verdict is Strong or Pivot, hand off to the Product Planner skill — it will use `docs/product-idea.md` as pre-filled context.
skills/product-planner/SKILL.md
+2 -2
View File
@@ -45,7 +45,7 @@ Generate documents from `docs/VISION.md`. See "Document Generation" below.
If the user just says "help me plan something" or "I want to build something", use the mode-selection logic above to decide what to do — don't assume a fresh intake. Only start the vision intake if `docs/VISION.md` does not exist.
**Validation nudge:** If `docs/product-idea.md` exists but `docs/validation-report.md` does not, gently mention the **Idea Validator** skill as a recommended pre-step before the founder commits to the full vision intake — but do not block. Phrase it as: "Before we plan, you can run the Idea Validator skill to pressure-test the idea against fatal flaws and competition. It usually surfaces a sharper target user and a smaller MVP. Want to validate first, or proceed straight to the intake?" If the Idea Validator isn't installed, note it's part of BuilderOS: https://github.com/BuildGreatProducts/BuilderOS. Honor the founder's choice without arguing.
**Validation nudge:** If `docs/product-idea.md` exists but `docs/validation-report.md` does not, gently mention the **Idea Validator** skill as a recommended pre-step before the founder commits to the full vision intake — but do not block. Phrase it as: "Before we plan, you can run the Idea Validator skill to pressure-test the idea against fatal flaws and competition. It usually surfaces a sharper target user and a smaller MVP. Want to validate first, or proceed straight to the intake?" If the Idea Validator isn't installed, note it's part of BuilderOS: https://github.com/BuildGreatProducts/builder-os. Honor the founder's choice without arguing.
-----
@@ -256,7 +256,7 @@ When all three documents are written, tell the user:
> - Run a **Build Loop** skill to start building from the roadmap
> - Run the **Launch Checklist** skill when you're ready to go live"
If any of those skills aren't installed, note they're all part of BuilderOS: https://github.com/BuildGreatProducts/BuilderOS.
If any of those skills aren't installed, note they're all part of BuilderOS: https://github.com/BuildGreatProducts/builder-os.
-----