planner
This skill should be used when the user asks to "plan a feature", "create feature plan", "start planning", "new feature", or wants comprehensive planning with analysis, spec, research, design, and TDD task breakdown.
What this skill does
# Feature Planning Session
Create a comprehensive feature planning artifact for: **$ARGUMENTS**
This planning session follows the Feature Planning Methodology documented in `aidocs/feature-planning-methodology.md`.
## Session Initialization
### Step 1: Determine Feature ID
Run this command to find the next feature number:
```bash
{ ls backlog/plans/ 2>/dev/null; ls backlog/plans/_completed/ 2>/dev/null; } | grep -E '^[0-9]{3}' | sort -r | head -1
```
The Feature ID format is `{NNN}-{slug}` where:
- `NNN` = 3-digit sequential number (001, 002, 003...)
- `slug` = lowercase, hyphenated descriptor (2-4 words)
### Step 2: Create Branch and Folder Structure
```bash
git checkout -b feature/{NNN}-{slug}
mkdir -p backlog/plans/{NNN}-{slug}/contracts
```
**Note**: When feature is complete, move folder to `backlog/plans/_completed/{NNN}-{slug}/`
### Step 3: Create Planning Artifacts
Create all artifacts in sequence using templates from `references/templates.md`.
---
## Planning Phases
### Phase 1: Analysis (`analysis.md`)
**Goal**: Understand the problem space, existing code, and patterns.
Key sections:
- Executive Summary with pattern/integration mapping
- Architecture Comparison (current vs target)
- Pattern Mapping from existing codebase
- What Exists vs What's Needed
- Key Insights (what works, gaps/limitations)
### Phase 2: Specification (`spec.md`)
**Goal**: Define requirements from user perspectives.
Key sections:
- Problem Statement and Solution Summary
- User Stories with Acceptance Criteria
- Functional Requirements (FR-1, FR-2, etc.)
- Non-Functional Requirements (performance, security)
- Scope (in/out/future)
- Success Criteria, Assumptions, Risks
### Phase 3: Research (`research.md`)
**Goal**: Validate design against external specifications, APIs, or standards.
Key sections:
- Conformance Analysis against external specs
- Gap identification
- Recommendations (critical, minor, future)
### Phase 4: Design
Create three artifacts:
**4a. Implementation Plan (`plan.md`)**
- Architecture diagrams (ASCII)
- Component responsibilities
- File structure with MODIFY/NEW annotations
- Key design decisions with rationale
- Risk mitigation
**4b. Data Model (`data-model.md`)**
- Entity definitions with fields/types
- Relationships and invariants
- State transitions
- Validation rules
**4c. Contracts (`contracts/`)**
- Interface definitions
- API schemas
- Configuration schemas
### Phase 5: Task Breakdown (`tasks.md`)
Organize tasks by phase with TDD workflow:
- `[TEST]` tasks: Write failing tests first
- `[IMPL]` tasks: Implement to pass tests
Include dependency diagram and task summary table.
---
## Session Workflow
### Execution Order
1. **Initialize**: Determine Feature ID, create branch and folders
2. **Phase 1**: Create `analysis.md` - understand problem space
3. **Phase 2**: Create `spec.md` - define requirements
4. **Phase 3**: Create `research.md` - validate against external specs (if applicable)
5. **Phase 4**: Create `plan.md`, `data-model.md`, `contracts/` - design
6. **Phase 5**: Create `tasks.md` - task breakdown
7. **Cleanup**: Remove the corresponding quick plan from `backlog/plans/` (e.g., `backlog/plans/YYYYMMDD-{slug}.md`) since the full planning artifacts supersede it
### Interactive Planning
As work progresses through each phase:
- Read relevant existing code to inform analysis
- Ask clarifying questions about requirements
- Research external APIs/specs as needed
- Validate design decisions with the user
### Output Summary
After completing all phases, summarize:
```
Feature: {NNN}-{slug}
Branch: feature/{NNN}-{slug}
Created Artifacts:
├── backlog/plans/{NNN}-{slug}/
│ ├── analysis.md ✅
│ ├── spec.md ✅
│ ├── research.md ✅
│ ├── plan.md ✅
│ ├── data-model.md ✅
│ ├── tasks.md ✅
│ └── contracts/
│ └── README.md ✅
Cleaned Up:
- Removed quick plan: backlog/plans/YYYYMMDD-{slug}.md 🗑️
Next Steps:
1. Review planning artifacts
2. Commit: git add backlog/plans/{NNN}-{slug} specs/tests/{NNN}-{slug}.md && git commit -m "feat: planning for {NNN}-{slug}"
3. Begin implementation: /work-plan {NNN}
4. When complete: mv backlog/plans/{NNN}-{slug} backlog/plans/_completed/
```
---
## Additional Resources
### Reference Files
For detailed templates and guidance, consult:
- **`references/templates.md`** - Full templates for all planning artifacts
### External References
- [Feature Planning Methodology](../aidocs/feature-planning-methodology.md)
- [Developer Guide](../docs/developer-guide.md)
- [Example: 001-mcp-integration](../backlog/plans/_completed/001-mcp-integration/)
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.