SkillFoxx

PLAID skill

Idea stress test, PRD with a roadmap, design tokens, a launch plan and a phase-by-phase build in one skill for founders.

  • 222 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • The Build phase writes application code from the roadmap and makes git commits after each phase.
  • For Figma mockups the skill can read files through a connected Figma MCP.
All reasons and checks

buildgreatproducts/plaidAuthor:BuildGreatProducts

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/plaid

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The Build phase writes application code from the roadmap and makes git commits after each phase.
  • For Figma mockups the skill can read files through a connected Figma MCP.

This is third-party code. Review the repository files before installing.

What it does

PLAID is one skill with six capabilities that take a founder from an idea to a launched product. Idea mines business processes and personal expertise and produces `docs/product-idea.md`. Validate stress-tests the chosen idea for fatal flaws, problem reality, competition and the first ten customers, scores it on six axes and writes `docs/validation-report.md`. Plan runs an eight-section interview, saves the answers to `vision.json` and generates `product-vision.md`, `prd.md` and `product-roadmap.md`. Design turns screenshots, mockups and Figma links into `docs/design.md` with tokens in Google's design.md format. Launch builds a go-to-market plan, `gtm.md`. Build works through the roadmap phase by phase, ticks off tasks, reviews code after each phase and commits to git. Capabilities switch on with phrases such as "plaid validate" or "plaid build".

Who it is for. Entrepreneurs and solo developers without a ready idea or spec who want to go all the way to a working app with a single agent.

Good fit when

  • There is no product idea yet and it is being mined from your own workflows and expertise.
  • A chosen idea should be stress-tested before the first line of code, ending in a strong, weak or pivot verdict.
  • A vision, a PRD and a roadmap are wanted in a format a coding agent reads.
  • A design system is assembled from screenshots or a Figma mockup into a `design.md` file.
  • A roadmap is executed phase by phase, with a code review and a commit after each.

Not a fit when

  • The product already works and one feature needs a tweak: the skill builds a product from scratch.
  • Financial models or legal documents are required: the skill runs a conversation and writes product documents.
  • Autonomous commits are unacceptable: the Build phase records changes in git after every phase.

Example request

plaid validate. Pressure-test my idea and tell me what would kill it first.

Limitations

All capabilities live in one skill, so the launch phrases matter: "plaid idea", "plaid validate", "plaid design", "plaid launch", "plaid build". Launch needs `vision.json` and `docs/product-vision.md` from Plan, and Build reads `docs/product-roadmap.md` and `docs/prd.md`. Reading mockups by link needs the Figma MCP. The skill formulates verdicts and strategy but does not check the market against data: scores rest on your answers. The structure of `vision.json` is checked by `scripts/validate-vision.js`, so Node.js is needed. The last commit is dated May 2026.

How to disable. Delete the `plaid` folder from the agent's skills directory. The documents it created, `vision.json` and `docs/`, stay in the project.

FAQ

How do I install PLAID?

Run `npx skills add BuildGreatProducts/plaid`. Manually, add the path to `SKILL.md` to the `skills` array of `.claude/settings.json` or `~/.claude/settings.json`.

How does Idea differ from Validate?

Idea ranks 3–5 candidate ideas on five criteria and picks one. Validate stress-tests the chosen idea: fatal flaws, competition, the first ten customers, a two-week MVP test and a verdict.

Which documents does Plan create?

`vision.json` with the interview answers, then `product-vision.md`, `prd.md` and `product-roadmap.md`. The first suits founders and stakeholders, the second coding agents, the third phased execution.

How does Design work?

You provide screenshots, mockups or Figma links, the skill describes colors, typography and shapes, asks a few questions and writes `docs/design.md`: YAML tokens with explanations.

What does Build do?

It finds the first roadmap phase with open tasks, completes them against the PRD, ticks `- [x]`, reviews the code and commits to git after each phase.

Discussion

No questions or reviews yet.

Skills

Skills for validating an app idea: trends, competitors, pricing, retention, acquisition cost and a final verdict scored 0 to 100

SkillExtended access512

The prd-write skill for Codex: turns an idea, prototype and screenshots into a PRD with roles, flows, events and acceptance

SkillExtended access154

A skill that scores a startup idea on 14 dimensions with web research: scorecard, assumption ledger and HTML report.

SkillExtended access57

Eleven skills that test a business idea before launch: competitors, a panel of 100 buyers, pricing, a financial model and a 30-day plan

SkillExtended access3.4K

A Claude Code method: a gated PRD, 47 skills, hooks and a Markdown fact base so the agent remembers decisions between sessions.

WorkflowExtended access179

README in short

The name stands for Product Led AI Development. Validate adapts the Startup Pressure Test framework from a sibling BuildGreatProducts repository, and the design system format comes from Google's open design.md. The license is MIT.

README badge

Original SKILL.md

---
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:

Report a problem