plan-project
Orchestrates sequential project planning. First validates user intent via AskUserQuestion (MANDATORY), then spawns ui-ux-specialist to create ui-ux-plan.md, then tech-lead-specialist to create dev-plan.md from ui-ux-plan.md, then spawns frontend-specialist and backend-specialist in parallel to create their detailed plans from dev-plan.md, then spawns qa-specialist to create test-plan.md from dev-plan.md and backend-plan.md. Triggers on: plan, create plan, plan project, project plan, full plan, prd to plan.
What this skill does
# Plan Skill
Orchestrate a complete project planning workflow with sequential agent handoff and parallel specialist execution.
---
## Orchestration Flow
```
/plan
|
v
+----------------------------------------------------------+
| STEP 1: AskUserQuestion (MANDATORY) |
| - Validate user intent |
| - Locate PRD / gather project description |
| - Clarify scope, tech stack, priorities |
+----------------------------------------------------------+
|
v
+----------------------------------------------------------+
| STEP 2: Ensure /docs directory |
+----------------------------------------------------------+
|
v
+----------------------------------------------------------+
| STEP 3: ui-ux-specialist (SEQUENTIAL) |
| - Reads PRD |
| - Writes: docs/ui-ux-plan.md |
+----------------------------------------------------------+
|
v
+----------------------------------------------------------+
| STEP 4: tech-lead-specialist (SEQUENTIAL) |
| - Reads: docs/ui-ux-plan.md |
| - Writes: docs/dev-plan.md |
+----------------------------------------------------------+
|
v
+----------------------------------------------------------+
| STEP 5: PARALLEL — frontend + backend specialists |
| |
| frontend-specialist ──Read──> docs/dev-plan.md |
| ──Write─> docs/frontend-plan.md |
| |
| backend-specialist ──Read──> docs/dev-plan.md |
| ──Write─> docs/backend-plan.md |
+----------------------------------------------------------+
|
v
+----------------------------------------------------------+
| STEP 6: qa-specialist (SEQUENTIAL) |
| - Reads: docs/dev-plan.md + docs/backend-plan.md |
| - Writes: docs/test-plan.md |
+----------------------------------------------------------+
|
v
+----------------------------------------------------------+
| STEP 7: Report completion with file summary |
+----------------------------------------------------------+
```
---
## Step 1: Validate User Intent (MANDATORY)
**You MUST use AskUserQuestion before spawning any agents. Never skip this step.**
### 1.1 Locate PRD
Search for the PRD file first:
```
Glob: **/prd.md
Glob: **/PRD.md
Glob: docs/prd.md
```
### 1.2 Ask User — Project Scope
**ALWAYS ask this question regardless of PRD existence.**
```
AskUserQuestion:
question: "What would you like to plan? Please confirm the scope."
header: "Plan Scope"
options:
- label: "Full project from PRD"
description: "Plan the entire project from the PRD file"
- label: "Specific feature only"
description: "Plan a single feature or module"
- label: "I'll describe it now"
description: "No PRD — I'll describe what to plan"
```
### 1.3 Ask User — PRD Location (if not found automatically)
```
AskUserQuestion:
question: "Where is your PRD file located?"
header: "PRD Path"
options:
- label: "docs/prd.md (Recommended)"
description: "Standard location in docs folder"
- label: "prd.md (root)"
description: "In the project root directory"
- label: "I'll provide the path"
description: "Enter a custom file path"
```
### 1.4 Ask User — UI/UX Priority
```
AskUserQuestion:
question: "What is the UI/UX priority for this project?"
header: "UI Priority"
options:
- label: "Speed to market (Recommended)"
description: "Use shadcn defaults, minimal customization"
- label: "Custom brand design"
description: "Detailed design system, unique visual identity"
- label: "Accessibility first"
description: "WCAG AAA compliance, inclusive design"
```
### 1.5 Ask User — Tech Stack (if not specified in PRD)
```
AskUserQuestion:
question: "What tech stack should we use?"
header: "Tech Stack"
options:
- label: "Next.js + Supabase (Recommended)"
description: "Full-stack React with Postgres backend"
- label: "React + Express + PostgreSQL"
description: "Traditional stack with Node backend"
- label: "Already specified in PRD"
description: "Use what's defined in the PRD"
```
### Question Rules
- **MANDATORY:** You MUST ask at least the Plan Scope question (1.2) before proceeding
- Ask a maximum of **5 questions total**
- Skip questions that are already answered in the PRD
- Track: `questionsAsked` (start at 0, stop at 5)
- Do NOT proceed to Step 2 until user has answered
---
## Step 2: Ensure /docs Directory
Before spawning agents, ensure the output directory exists:
```
Bash: mkdir -p docs
```
---
## Step 3: Spawn ui-ux-specialist (SEQUENTIAL)
**This agent runs FIRST, alone. It creates the design foundation that all other plans depend on.**
```
Task:
subagent_type: ui-ux-specialist
description: "Create UI/UX plan"
prompt: |
Read the PRD at: {prd_path}
User preferences:
- UI Priority: {ui_priority from Step 1.4}
- Tech Stack: {tech_stack from Step 1.5}
- Scope: {scope from Step 1.2}
Write your complete ui-ux-plan.md to: docs/ui-ux-plan.md
Include:
- User research and personas
- Information architecture
- User flows
- Design system (colors, typography, spacing)
- Component library specifications
- Wireframes for all key pages
- Accessibility checklist (WCAG 2.1 AA minimum)
- Micro-interactions and animation guidelines
- Implementation guidelines for developer handoff
Write the file using the Write tool. Return "Done: docs/ui-ux-plan.md" when complete.
```
**Wait for this agent to complete before proceeding to Step 4.**
After the agent completes, verify the file was created:
```
Glob: docs/ui-ux-plan.md
```
If the file does not exist, report the error and stop. Do NOT proceed.
---
## Step 4: Spawn tech-lead-specialist (SEQUENTIAL)
**This agent runs SECOND. It reads ui-ux-plan.md and creates the single source of truth dev-plan.md.**
```
Task:
subagent_type: tech-lead-specialist
description: "Create dev plan from UI/UX"
prompt: |
Read the UI/UX plan at: docs/ui-ux-plan.md
Also read the PRD at: {prd_path}
Create dev-plan.md as the SINGLE SOURCE OF TRUTH for this project.
Translate the design decisions, wireframes, component specs, and accessibility
requirements from ui-ux-plan.md into a minimal, phased development checklist.
Phases:
- Phase 0: Foundation (project setup, design tokens)
- Phase 1: Backend (schema, API, RLS)
- Phase 2: Shared UI (src/components/)
- Phase 3: Features (src/features/)
- Phase 4: Integration (routing, API wiring)
- Phase 5: Polish (a11y, animations)
Every task must have:
- Output: file paths or artifacts
- Behavior: how it works
- Verify: concrete check steps
Write the file to: docs/dev-plan.md
Do NOT create progress.json — that is handled separately.
Write the file using the Write tool. Return "Done: docs/dev-plan.md" when complete.
```
**Wait for this agent to complete before proceeding to Step 5.**
After the agent completes, verify the file was created:
```
Glob: docs/dev-plan.md
```
If the file does not exist, report the error and stop. Do NOT proceed.
---
## Step 5: Spawn frontend-specialist + backend-specialist (PARALLEL)
**These two agents run IN PARALLEL. Both read dev-plan.md and write their own specialist plans.**
**CRITICAL: Spawn both agents in a SINGLE message with two Task tool calls.**
```
[Single message with 2 Task tool calls]
Task 1: frontend-specialist
subagent_type: frontend-specialist
description: "Create frontend plan"
prompt: |
ReRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct 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".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.