pipeline
Complete project generation pipeline with Task tool multi-agent orchestration. Requirements -> Design -> Tasks -> Project -> Implementation.
What this skill does
# AIDA Pipeline Skill
Complete automation pipeline for project generation using Task tool for multi-agent orchestration.
## Overview
This skill executes the full AIDA pipeline:
1. **Phases 1-4**: Specification (via Leader-Spec + Players)
2. **Phase 5**: Implementation (via Leader-Impl + TDD Players)
## Multi-Agent Architecture
```
[Pipeline Skill]
|
+-- Task tool --> [Leader-Spec]
| |
| +-- Task tool --> [Player] (haiku)
| +-- Task tool --> [Player] (haiku)
| |
| +--> .aida/specs/
|
+-- Task tool --> [Leader-Impl]
|
+-- Task tool --> [TDD Player] (haiku)
+-- Task tool --> [TDD Player] (haiku)
|
+--> [PROJECT]/
```
## Execution Flow
### Step 1: Initialize Session
```bash
mkdir -p .aida/state .aida/checkpoints .aida/artifacts/requirements .aida/artifacts/designs .aida/tasks .aida/results .aida/specs
```
Create session state:
```json
{
"session_id": "<UUID>",
"started_at": "<ISO8601>",
"mode": "pipeline",
"phase": 1,
"user_request": "<REQUEST>",
"project_name": "<PROJECT>"
}
```
### Step 2: Launch Leader-Spec (Phases 1-4)
**Use Task tool with these parameters:**
| Parameter | Value |
|-----------|-------|
| description | "Leader-Spec: specification phases" |
| subagent_type | "general-purpose" |
| run_in_background | false |
| prompt | See below |
**Prompt:**
```
You are AIDA Leader-Spec agent.
Read instructions: agents/leader-spec.md
Project: [PROJECT_NAME]
User Request: [USER_REQUEST]
Execute Phases 1-4:
Phase 1: Extraction & Architecture
- Spawn players for requirements and architecture
- Output: .aida/artifacts/requirements/
Phase 2: Structure & Schema
- Spawn players for structure and schema design
- Output: .aida/artifacts/designs/
Phase 3: Alignment
- Cross-check all artifacts
- Output: .aida/artifacts/alignment.md
Phase 4: Verification
- Consolidate final specs
- Output: .aida/specs/requirements.md
- Output: .aida/specs/design.md
- Output: .aida/specs/tasks.md
For parallel work, use Task tool with model: haiku.
When complete:
- Update .aida/state/session.json with phase: 5
- Write .aida/results/spec-complete.json
```
### Step 3: Launch Leader-Impl (Phase 5)
**Use Task tool with these parameters:**
| Parameter | Value |
|-----------|-------|
| description | "Leader-Impl: TDD implementation" |
| subagent_type | "general-purpose" |
| run_in_background | false |
| prompt | See below |
**Prompt:**
```
You are AIDA Leader-Impl agent.
Read instructions: agents/leader-impl.md
Project: [PROJECT_NAME]
Read specifications:
- .aida/specs/requirements.md
- .aida/specs/design.md
- .aida/specs/tasks.md
Execute Phase 5: TDD Implementation
1. Initialize project:
mkdir -p [PROJECT_NAME]/src
mkdir -p [PROJECT_NAME]/tests
2. For each task in tasks.md, spawn TDD player:
- Use Task tool with model: haiku
- Include TDD instructions (RED-GREEN-REFACTOR)
3. Quality gates:
- All tests pass
- Build succeeds
- Coverage >= 80%
When complete:
- Update .aida/state/session.json with phase: "completed"
- Write .aida/results/impl-complete.json
```
### Step 4: Report Completion
```
AIDA Pipeline Complete
Session: [SESSION_ID]
Project: [PROJECT_NAME]
Artifacts:
- Specs: .aida/specs/
- requirements.md
- design.md
- tasks.md
- Project: [PROJECT_NAME]/
Test Results:
- All tests passed
- Coverage: XX%
Next Steps:
cd [PROJECT_NAME]
npm install
npm run dev
```
## Phase Details
### Phase 1: Extraction & Architecture
Player tasks (parallel):
1. Extract functional requirements
2. Extract non-functional requirements
3. Design high-level architecture
Output:
- `.aida/artifacts/requirements/extraction.md`
- `.aida/artifacts/designs/architecture.md`
### Phase 2: Structure & Schema
Player tasks (parallel):
1. Define directory structure
2. Design data schemas
3. Create API contracts
Output:
- `.aida/artifacts/designs/structure.md`
- `.aida/artifacts/designs/schemas.md`
- `.aida/artifacts/designs/api.md`
### Phase 3: Alignment
Tasks:
1. Cross-check requirements
2. Verify architecture supports features
3. Identify gaps
Output:
- `.aida/artifacts/alignment.md`
### Phase 4: Verification
Tasks:
1. Final review
2. Consolidate specs
3. Generate task breakdown
Output:
- `.aida/specs/requirements.md`
- `.aida/specs/design.md`
- `.aida/specs/tasks.md`
### Phase 5: TDD Implementation
For Next.js + TypeScript + Prisma project:
```bash
cd [PROJECT_NAME]
npx create-next-app@latest . --typescript --tailwind --eslint --app --src-dir --import-alias "@/*" --use-npm --yes
npm install prisma @prisma/client
npx prisma init
```
TDD Player tasks (parallel):
1. Implement feature 1 (RED-GREEN-REFACTOR)
2. Implement feature 2 (RED-GREEN-REFACTOR)
3. Implement feature 3 (RED-GREEN-REFACTOR)
Output:
- `[PROJECT_NAME]/`
## Error Handling
If a phase fails:
1. Check `.aida/results/` for error reports
2. Review `.aida/state/session.json`
3. Options:
- Fix issue and use `/aida:work` to continue
- Restart with `/aida:pipeline`
## Notes
1. **Sequential phases** - Wait for each Leader to complete
2. **Parallel players** - Leaders spawn multiple players in parallel
3. **TDD enforced** - Phase 5 uses RED-GREEN-REFACTOR
4. **File-based state** - All state in .aida/
5. **Task tool required** - Subagent orchestration
Related 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.