Plaid
Walk from raw founder context through Idea, Validate, Plan, Design, Launch, and Build with conversational gates and docs/ artifacts.
Overview
PLAID is a journey-wide agent skill that guides solo founders from product ideation through validation, planning, design specs, go-to-market, and roadmap build execution via structured PLAID conversations.
Install
npx skills add https://github.com/buildgreatproducts/plaid --skill plaidWhat is this skill?
- Six capabilities: Idea, Validate, Plan, Design, Launch, and Build in one PLAID workflow
- Validate mode pressure-tests fatal flaws, problem reality, competition, and 2-week MVP feasibility
- Plan generates PRD-style strategy from vision intake into docs/
- Design translates image references into design.md and design tokens
- Launch produces go-to-market and launch playbook conversations
- Six named capabilities: Idea, Validate, Plan, Design, Launch, Build
- Documented pipeline: Idea → Validate → Plan → Launch → Build (v2.0)
Adoption & trust: 516 installs on skills.sh; 194 GitHub stars; 2/3 security scanners passed (skills.sh audits).
Who is it for?
Indie founders shipping a SaaS or agent-backed product who want one named workflow (PLAID) instead of ad-hoc prompts per phase.
Skip if: Pure engineering tasks with an approved spec already locked—skip PLAID Idea/Validate when you only need a codegen integration skill.
When should I use this skill?
User says PLAID, plaid idea/validate/design/launch/build, help find or validate an idea, pressure-test, PRD/vision, design from image, GTM, or execute the roadmap.
What do I get? / Deliverables
You accumulate phased docs under docs/ (vision, validation, PRD, design.md, GTM, build roadmap) so the agent can execute the next PLAID capability in order.
- Phase artifacts under docs/ (validation notes, PRD/strategy, design.md, launch/GTM drafts, build roadmap)
- Structured conversation outcomes per PLAID capability
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Mine a concrete product idea from the founder’s domain expertise using PLAID Idea prompts.
Run Validate to surface fatal flaws, competition, and whether a 2-week MVP is realistic.
Produce PRD and design.md from vision intake and reference images before implementation.
Draft GTM and launch plan conversations once the product definition is stable.
Invoke Build to execute the roadmap after Plan and optional Validate outputs exist.
How it compares
End-to-end founder pipeline in one skill package, not a single-phase landing-page generator or a deployment MCP.
Common Questions / FAQ
Who is plaid for?
Solo founders and indie builders using AI agents who need structured movement from idea discovery through validation, planning, design, launch, and build with written artifacts.
When should I use plaid?
Use it across Idea (find an idea), Validate (pressure-test fatal flaws), Validate/Build boundary (PRD and design.md), Launch (GTM), and Build (execute roadmap)—whenever triggers like “plaid validate,” “generate a PRD,” or “plaid launch” appear.
Is plaid safe to install?
It requires filesystem access to write docs/; review the Security Audits panel on this page and restrict write paths in your agent config before running in a sensitive repo.
SKILL.md
READMESKILL.md - Plaid
## 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` →