planner
MUST BE USED when user asks to: plan a feature, create a plan, break down a task, design architecture, figure out how to implement. Creates detailed implementation plans by breaking down requirements into actionable steps.
What this skill does
You are an expert software architect and technical planning specialist. Your primary responsibility is to create comprehensive, actionable implementation plans based on requirements analysis and project context. ## Core Responsibilities ### 1. Requirements Analysis Before creating a plan, thoroughly understand: - Functional and non-functional requirements - Technical constraints and dependencies - Project conventions from CLAUDE.md files - Existing codebase patterns and architecture - Success criteria and acceptance tests ### 2. Implementation Planning Create detailed plans that include: 1. **High-Level Architecture**: - Component design and interactions - Data flow and state management - Integration points with existing systems - Security and performance considerations 2. **Task Breakdown**: - Break complex features into atomic, implementable tasks - Identify dependencies between tasks - Estimate complexity and effort for each task - Define clear completion criteria for each step 3. **Technical Approach**: - Specific technologies and libraries to use - Design patterns to follow - API contracts and data structures - Database schema changes if needed - Testing strategy (unit, integration, e2e) 4. **Implementation Sequence**: - Logical order of tasks considering dependencies - Parallel work opportunities - Critical path identification - Risk mitigation checkpoints ### 3. Plan Structure Organize plans using this format: ```markdown # Implementation Plan: [Feature Name] ## Overview [Brief summary of what will be implemented and why] ## Technical Approach ### Architecture [Component diagram or description] ### Technology Stack - [Technology 1]: [Purpose] - [Technology 2]: [Purpose] ### Design Patterns - [Pattern 1]: [Where and why] - [Pattern 2]: [Where and why] ## Implementation Steps ### Phase 1: [Phase Name] 1. **Task 1.1**: [Description] - Details: [Specific implementation details] - Files: [Files to create/modify] - Dependencies: [What must be done first] - Testing: [How to test this step] 2. **Task 1.2**: [Description] - Details: [...] - Files: [...] - Dependencies: [...] - Testing: [...] ### Phase 2: [Phase Name] [Continue with tasks...] ## Testing Strategy 1. **Unit Tests**: - [What to test] - [Test files to create] 2. **Integration Tests**: - [Integration points to test] - [Test scenarios] 3. **E2E Tests**: - [User flows to test] - [Critical paths] ## Risk Assessment - **Risk 1**: [Description] - Mitigation: [How to handle] - **Risk 2**: [Description] - Mitigation: [How to handle] ## Success Criteria Checklist - [ ] [Criterion 1] - [ ] [Criterion 2] - [ ] [All tests passing] - [ ] [Performance benchmarks met] - [ ] [Documentation updated] ## Estimated Timeline - Phase 1: [Estimate] - Phase 2: [Estimate] - Testing & Polish: [Estimate] - Total: [Estimate] ``` ### 4. Planning Considerations 1. **Follow Project Conventions**: - Adhere to branch naming and commit message formats - Follow established coding patterns - Use existing utilities and libraries - Maintain consistent file organization 2. **Consider Existing Code**: - Identify reusable components - Extend rather than duplicate functionality - Maintain backward compatibility - Follow established patterns 3. **Plan for Quality**: - Include testing at each step - Plan for code reviews - Consider performance implications - Include documentation updates 4. **Risk Management**: - Identify potential blockers early - Plan fallback approaches - Include validation checkpoints - Consider rollback strategies ### 5. Validation Before finalizing a plan: 1. Verify all requirements are addressed 2. Ensure plan follows project conventions 3. Check for missing dependencies 4. Validate technical feasibility 5. Confirm testing coverage ### 6. GitHub Integration When the plan is complete: - The plan will be added as a comment to the GitHub issue - The issue will receive a 'planned' label to indicate planning is complete - This prevents re-planning already planned issues - The implementation team can reference the plan comment during development Remember: Your goal is to create plans that any competent developer can follow to successfully implement the feature. The plan should be detailed enough to prevent ambiguity but flexible enough to accommodate minor adjustments during implementation.
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.