plaid — скилл для Claude Code: что делает и как установить
Проводит фаундера от формулировки идеи до запуска продукта. Скилл тестирует концепцию на жизнеспособность, пишет PRD и готовит роадмап разработки.
npx skills add BuildGreatProducts/plaid --skill plaid -a claude-codeЧто делает plaid
Скилл выстраивает пайплайн продуктовой разработки из шести этапов: Idea, Validate, Plan, Design, Launch и Build. На шаге проверки идея тестируется на фатальные изъяны, реальность проблемы, силу конкурентов и возможность собрать MVP за две недели. Для проектирования интерфейса скилл принимает скриншоты или ссылки на макеты и извлекает из них токены в docs/design.md.
Работа сохраняется между сессиями. Прогресс фиксируется в файлах каталога docs/ и конфигурации vision.json. Перед генерацией документов агент запускает валидацию схемы командой node scripts/validate-vision.js --migrate, поэтому в среде должен быть установлен Node.js.
Если у агента нет прав на запись в файловую систему проекта для создания папки docs/, пайплайн не сможет сохранить артефакты и прервётся.
Какие задачи решает
- проверить жизнеспособность идеи и собрать MVP за две недели
- составить PRD и зафиксировать продуктовое видение в vision.json
- извлечь дизайн-токены из скриншота или референса в docs/design.md
- подготовить стратегию выхода на рынок и запустить реализацию роадмапа
Примеры запросов агенту
- Помоги найти и сформулировать идею продукта через plaid idea
- Проверь мою идею на фатальные недостатки с помощью plaid validate
- Собери design.md и дизайн-токены по этому скриншоту интерфейса
Как установить plaid
1Через Skills CLI (Vercel)
npx skills add BuildGreatProducts/plaid --skill plaid -a claude-code2Вручную: положить файлы
~/.claude/skills/plaid/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/plaid/
1Через Skills CLI (Vercel)
npx skills add BuildGreatProducts/plaid --skill plaid -a codex2Вручную: положить файлы
.agents/skills/plaid/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add BuildGreatProducts/plaid --skill plaid -a cursor2Вручную: положить файлы
.cursor/skills/plaid/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install BuildGreatProducts/plaid plaid2Вручную: положить файлы
.github/skills/plaid/SKILL.md1Через Skills CLI (Vercel)
npx skills add BuildGreatProducts/plaid --skill plaid -a gemini-cli2Командой платформы
gemini skills install https://github.com/BuildGreatProducts/plaidВручную: положить файлы
.devin/skills/plaid/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add BuildGreatProducts/plaid --skill plaid -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о plaid
Как установить plaid в Claude Code?
Выполните команду npx skills add BuildGreatProducts/plaid --skill plaid -a claude-code. Также файл скилла можно сохранить вручную по пути ~/.claude/skills/plaid/SKILL.md.
Что делает скилл plaid?
Он ведёт структурированный диалог для проверки гипотезы, сохраняет спецификацию в vision.json, генерирует PRD в каталоге docs/ и контролирует задачи в роадмапе.
Что требуется для запуска проверок plaid?
В системе должен быть доступен Node.js для вызова node scripts/validate-vision.js --migrate, а у агента должен быть доступ к локальной файловой системе для записи в каталог docs/.
Исходный текст
SKILL.md · MIT
--- name: plaid description: | 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", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap". license: MIT metadata: author: plaid-dev version: "2.0" compatibility: Requires file system access to write docs/ directory. --- ## Overview 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. ## 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 `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. ## Routing 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` | ### Auto-detection If the request is ambiguous, check the project state to determine the right capability: - No `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) - No `vision.json` → route to Plan - `vision.json` exists but `docs/` is incomplete → route to Plan (document generation mode) - All docs exist but no code built yet → suggest Launch or Build - `docs/product-roadmap.md` has unchecked tasks → route to Build - User shares an image, screenshot, or Figma URL with no other clear intent → offer Design Design 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. ### Phase Transitions 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. - After Idea completes → suggest Validate (`/plaid validate`) to pressure-test before planning; Plan (`/plaid`) is a valid fast-forward if the founder is confident - After Validate completes with a Strong verdict → suggest Plan (`/plaid`); `docs/product-idea.md` was sharpened during validation and pre-fills much of the vision intake - After Validate completes with a Pivot verdict → re-run Validate against the pivoted framing, or return to Idea (`/plaid idea`) to rework candidates - After Validate completes with a Weak verdict → recommend more discovery before Plan; do not advance automatically - After Plan completes → suggest Design (`/plaid design`) if the founder has imagery to anchor on, then launching (`/plaid launch`) or building (`/plaid build`) - After Design completes → if `docs/prd.md` does not yet exist, suggest Plan (`/plaid plan`); if it does, suggest Build (`/plaid build`) - After Launch completes → suggest building (`/plaid build`) - After Build completes → suggest launching (`/plaid launch`) if not done already
© plaid-dev · MIT · BuildGreatProducts/plaid