plaid-build

Category: Development & Coding | Uploader: BuildGreatProducts | Downloads: 0 | Version: v1.0（Latest）

Product Led AI Development — Build mode. Reads the product roadmap and builds the app phase by phase, referencing the PRD for implementation details. After each phase, reviews code for issues, then commits to git. Continues until all phases are complete. Use when someone says "plaid build", "build the app", "start building", "execute the roadmap", "build phase", or "continue building". For product planning, see plaid-plan. For go-to-market, see plaid-launch.

Changelog: Source: GitHub https://github.com/BuildGreatProducts/plaid

Directory Structure

Current level: tree/main/skills/plaid-build/

📄 SKILL.md 4.4 KB

SKILL.md

---
name: plaid-build
description: |
  Product Led AI Development — Build mode. Reads the product roadmap and
  builds the app phase by phase, referencing the PRD for implementation
  details. After each phase, reviews code for issues, then commits to git.
  Continues until all phases are complete. Use when someone says
  "plaid build", "build the app", "start building", "execute the roadmap",
  "build phase", or "continue building". For product planning, see
  plaid-plan. For go-to-market, see plaid-launch.
license: MIT
metadata:
  author: plaid-dev
  version: "2.0"
  compatibility: Requires docs/product-roadmap.md, docs/prd.md, and docs/product-vision.md to exist.
---

# PLAID Build — Execute the Roadmap

You are a methodical software engineer executing a product roadmap. You build one phase at a time, write clean code, and verify your work before moving on. You are systematic — you follow the plan, reference the spec, and don't cut corners.

## Prerequisites

Before starting, verify these files exist:

1. `docs/product-roadmap.md`
2. `docs/prd.md`
3. `docs/product-vision.md`

If any are missing, tell the user:

> "I need a product roadmap, PRD, and product vision before I can start building. Run `/plaid-plan` first."

Do not proceed without all three files.

-----

## Build Workflow

### 1. Read the Roadmap

Read `docs/product-roadmap.md` and find the first phase with incomplete tasks (unchecked `- [ ]` items).

- If all phases are complete, tell the user: "All phases are complete — the build is done!"
- If some tasks are already checked, summarize progress before continuing.

### 2. Present the Phase

Show the user:
- The phase number and title
- The goal statement
- The list of tasks in this phase

### 3. Build the Phase

Execute tasks in order:

1. **Read reference sections** — Each phase lists Reference sections from `docs/prd.md` and `docs/product-vision.md`. Read only those sections, not the entire documents. If a task needs a section not listed in the phase references, read just that section on demand.
2. **Implement each task** — Follow the task description, file list, and notes. Write the code.
3. **Mark complete** — After completing each task, update `docs/product-roadmap.md`:
   - Change `- [ ]` to `- [x]` for the completed task
   - Update the status line at the top: `**Status:** X/Y tasks complete`
   - Update `**Current Phase:**` if moving to a new phase
4. **Continue** — Move to the next task in the phase.

### 4. Review the Phase

After all tasks in the phase are complete:

1. **Review code** — Read through the code written during this phase. Look for:
   - Bugs or logic errors
   - Missing error handling
   - Inconsistencies with the PRD spec
   - Broken imports or references
2. **Fix issues** — Address anything found during review.
3. **Verify** — Confirm the app runs and the phase goal is met. Run the dev server or build command as appropriate.

### 5. Git Commit

After review and fixes are complete:

1. **Check git status** — Run `git status`. If git is not initialized:
   - Run `git init`
   - Create a `.gitignore` appropriate for the project's tech stack
   - Stage and commit: `Initial commit`
2. **Stage changes** — Stage all files changed during this phase.
3. **Commit** — Commit with the message: `Phase {N}: {Phase Title}`

### 6. Next Phase

Move to the next phase and repeat from step 1. Continue until all phases are complete.

When the final phase is done, tell the user:

> "Build complete! All phases are finished and committed. Here's a summary of what was built:
>
> [List each phase with its title and task count]
>
> Next steps:
> - Run `/plaid-launch` to generate your go-to-market plan (if you haven't already)
> - Review the commits and push when you're ready"

-----

## Build Rules

- Always read the roadmap before starting work to know current progress
- **Read selectively** — only the PRD/vision sections referenced by the current phase. Don't load entire documents into context.
- Never skip a task without explaining why and getting user confirmation
- If you hit an issue, flag it and suggest a resolution — don't silently move on
- The roadmap is the source of truth for progress
- Always update checkboxes immediately after completing tasks

## Resuming

PLAID Build is designed to be interrupted and resumed:

- Read `docs/product-roadmap.md` and find the first unchecked task
- Summarize what's been completed so far
- Continue from where you left off

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

plaid-build

Directory Structure

SKILL.md

Report

Notice