Build Mvp
BuildGreatProducts/builder-os
Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents.
Product Led AI Development — guides founders from idea to launched product.
$ npx skills add BuildGreatProducts/plaid --skill plaid -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuildGreatProducts/plaid plaid --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plaid" agent skill from https://github.com/BuildGreatProducts/plaid/tree/main into .claude/skills/plaid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plaid", 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.
$ npx skills add BuildGreatProducts/plaid --skill plaid -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuildGreatProducts/plaid plaid --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plaid" agent skill from https://github.com/BuildGreatProducts/plaid/tree/main into .agents/skills/plaid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plaid", 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/plaid --skill plaid -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuildGreatProducts/plaid plaid --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plaid" agent skill from https://github.com/BuildGreatProducts/plaid/tree/main into .cursor/skills/plaid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plaid", 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.
$ npx skills add BuildGreatProducts/plaid --skill plaid -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuildGreatProducts/plaid plaid --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plaid" agent skill from https://github.com/BuildGreatProducts/plaid/tree/main into .gemini/skills/plaid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plaid", 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/plaid plaidInstalls 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/plaid --skill plaid -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plaid" agent skill from https://github.com/BuildGreatProducts/plaid/tree/main into .github/skills/plaid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plaid", 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/plaid --skill plaid -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/plaid plaid --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plaid" agent skill from https://github.com/BuildGreatProducts/plaid/tree/main into .opencode/skills/plaid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plaid", 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.
plaidProduct Led AI Development — guides founders from idea to launched product.
Plaid is an agent skill from BuildGreatProducts/plaid. Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business"…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files, including scripts, reference files and assets (for example `README.md`, `assets/vision-template.json` and `package.json`).
It sits in Product & Project Management, covering Design tokens, Go-to-market strategy and Product strategy. The repository describes itself as: Agent skill for the PLAID development methodology. The licence is MIT.
Read from SKILL.md and the folder at commit 002ea93. It shows what the files ask for, not the result of running them.
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.
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
nodeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Plaid loads about 1.6k tokens when it runs, and up to ~41k if it reads all its reference files. Until then it costs about 253 tokens; SKILL.md has 689 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.
The automated check found no risky patterns in SKILL.md.
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); the scripts in this folder are not scanned.
The full file from BuildGreatProducts/plaid at commit 002ea93, republished under its MIT licence (© BuildGreatProducts). 689 words, ~1,567 tokens.
.claude/skills/plaid/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.PLAID helps founders go from idea to launched product through structured conversations and AI-powered document generation. The full pipeline is: Idea → Validate → Plan → Launch → Build. Validate is optional but strongly recommended — it pressure-tests the idea before the founder commits to the full vision intake. Design is a side capability that can run at any point — typically alongside Plan or before Build — to translate image references into a docs/design.md token spec.
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 vision.json, always validate first by running node scripts/validate-vision.js --migrate. The --migrate flag automatically upgrades older schema versions. If validation fails after migration, report errors and fix them before proceeding.
Resumability: PLAID is designed to be interrupted and resumed at any point. Always check the current project state before starting work — does vision.json exist? Are docs present? What's the roadmap progress? Pick up from where things left off.
Determine which capability the user needs based on their request, then read the appropriate reference file and follow its instructions:
| User Intent | Reference File |
|---|---|
| "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "what should I build" | references/idea.md |
| "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "stress test my idea" | references/validate.md |
| "PLAID", "plan a product", "define my vision", "generate a PRD", "plan my app", "spec out my idea", "product strategy", "help me build something" | references/plan.md |
| "plaid design", "design from image", "translate image to design", "create design.md", "image to design system", "extract design tokens", "design system from screenshot" | references/design.md |
| "plaid launch", "go-to-market", "launch plan", "GTM strategy", "help me launch", "marketing plan", "launch playbook" | references/launch.md |
| "plaid build", "build the app", "start building", "execute the roadmap", "build phase", "continue building" | references/build.md |
If the request is ambiguous, check the project state to determine the right capability:
docs/product-idea.md AND no vision.json → offer Idea (with Plan as a direct alternative if they already know what they want to build)docs/product-idea.md exists but no docs/validation-report.md AND no vision.json → suggest Validate (with Plan as a fast-forward if the founder is confident)docs/product-idea.md and docs/validation-report.md exist but no vision.json → route to Plan (using docs/product-idea.md as pre-filled context)vision.json → route to Planvision.json exists but docs/ is incomplete → route to Plan (document generation mode)docs/product-roadmap.md has unchecked tasks → route to BuildDesign is image-triggered and orthogonal to the main pipeline — it does not require any other PLAID document. Route to it whenever the founder's intent centers on translating visual references into a design system, regardless of pipeline state.
If still ambiguous after checking state, ask one clarifying question before loading a reference file.
When a capability completes, suggest the natural next step. If the user progresses naturally from one capability to the next during a session (e.g., finishes idea discovery and says "now let's plan"), load the next reference file and continue without requiring re-invocation.
/plaid validate) to pressure-test before planning; Plan (/plaid) is a valid fast-forward if the founder is confident/plaid); docs/product-idea.md was sharpened during validation and pre-fills much of the vision intake/plaid idea) to rework candidates/plaid design) if the founder has imagery to anchor on, then launching (/plaid launch) or building (/plaid build)docs/prd.md does not yet exist, suggest Plan (/plaid plan); if it does, suggest Build (/plaid build)/plaid build)/plaid launch) if not done already© BuildGreatProducts, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 20 other files (scripts, references, assets) in the repository root of BuildGreatProducts/plaid.
Open the folder on GitHubat commit 002ea93
Plaid 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 |
|---|---|---|---|---|---|---|
| Plaid this skillBuildGreatProducts/plaid | 218 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Build MvpBuildGreatProducts/builder-os | 228 | — | ~1.2k | Automated safety check: Notes | MIT | |
| Prd V02 Product Type Classificationmattgierhart/PRD-driven-context-engineering | 180 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Prd V09 Hn Reddit Launchmattgierhart/PRD-driven-context-engineering | 180 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Openprd UI ContextDavidLam-oss/obsidian-wechat-converter | 335 | — | ~899 | Automated safety check: Pass | MIT | |
| Organic Growth Path Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~5.2k | Automated safety check: Pass | Custom licence |
BuildGreatProducts/builder-os
Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents.
mattgierhart/PRD-driven-context-engineering
Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape.
mattgierhart/PRD-driven-context-engineering
Build a Hacker News + Reddit launch playbook for developer-tools and community-led products during PRD v0.9 Go-to-Market.
DavidLam-oss/obsidian-wechat-converter
OpenPrd UI Context skill:区分 greenfield、brownfield 与局部修正,基于已确认 PRD、可选 CodeGraph 和本地证据提出专业 UI/UX 方向,并在用户确认后编译 PRODUCT.md、DESIGN.md 和 Impeccable handoff。
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Digidai/product-manager-skills
PM skill for Claude Code, Codex, Cursor, and Windsurf. An agent skill from Digidai/product-manager-skills.
Product Led AI Development — guides founders from idea to launched product. Plaid is an agent skill from BuildGreatProducts/plaid. Product Led AI Development — guides founders from idea to launched product.
Plaid fits situations like: someone says PLAID; help me find an idea; idea from my business; idea from my expertise.
Run `npx skills add BuildGreatProducts/plaid --skill plaid -a claude-code`. Or copy the skill folder (the BuildGreatProducts/plaid repository) into .claude/skills/plaid in your project. Claude Code loads it when a task matches its description.
Run `npx skills add BuildGreatProducts/plaid --skill plaid -a codex`. Or copy the skill folder (the BuildGreatProducts/plaid repository) into .agents/skills/plaid in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BuildGreatProducts/plaid --skill plaid -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plaid, .gemini/skills/plaid, .github/skills/plaid and .opencode/skills/plaid in your project.
Going by SKILL.md and its folder, Plaid needs the command-line tools its instructions call (node).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Plaid is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 39k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Plaid: Build Mvp (BuildGreatProducts/builder-os, 228 stars), Prd V02 Product Type Classification (mattgierhart/PRD-driven-context-engineering, 180 stars), Prd V09 Hn Reddit Launch (mattgierhart/PRD-driven-context-engineering, 180 stars) and Openprd UI Context (DavidLam-oss/obsidian-wechat-converter, 335 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
BuildGreatProducts (a GitHub user) maintains it in BuildGreatProducts/plaid, which has 218 GitHub stars. The repository was last updated on May 8, 2026.
Source: BuildGreatProducts/plaid on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.