planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
What this skill does
# Planner Agent Create detailed, phased implementation plans for bugs, features, or tasks. ## Process ### Phase 0: Research 1. **Investigate the codebase:** - Architecture and patterns - Similar existing implementations - Dependencies and frameworks - Related components 2. **Analyze the request:** - Core requirements - Challenges & edge cases - Security/performance/UX considerations ### Phase 1: Clarify Requirements Before doing ANY documentation search: clarify requirements with user. This will narrow and aid you in finding the right docs. Think of 5-10 questions that will help you generate the best plan possible. Here are suggested example categories, but not a strict or exhaustive list. You may ask anything helpful. Use best judgement & prioritize ambiguity and risk reduction: 1. Goals & success criteria 2. Scope & non‑goals 3. Users & core workflows 4. Platforms & environments 5. Tech constraints 6. Data & integrations 7. Auth & permissions 8. Performance & reliability 9. Testing & validation 10. Ask any helpful question ### Phase 2: Retrieve Documentation When the plan involves any external library, API, framework, or service, use the Context7 skill to fetch the latest official docs before drafting tasks. This ensures version‑accurate steps, correct parameters, and current best practices. If no external dependencies apply, skip this phase. ### Phase 3: Create Plan #### Structure - **Overview**: Brief summary and approach - **Sprints**: Logical phases that build on each other - **Tasks**: Specific, actionable items within sprints #### Sprint Requirements Each sprint must: - Result in **demoable, runnable, testable** increment - Build on prior sprint work - Include demo/verification checklist #### Task Requirements Each task must be: - **Atomic and committable** (small, independent) - Specific with clear inputs/outputs - Independently testable - Include file paths when relevant - Include dependencies for parallel execution - Include tests or validation method **Bad:** "Implement Google OAuth" **Good:** - "Add Google OAuth config to env variables" - "Install passport-google-oauth20 package" - "Create OAuth callback route in src/routes/auth.ts" - "Add Google sign-in button to login UI" ### Phase 3: Save Save the file Generate filename from request: 1. Extract keywords 2. Convert to kebab-case 3. Add `-plan.md` suffix Examples: - "fix xyz bug" → `xyz-bug-plan.md` ### Phase 4: Gotchas AFTER it is saved. Identify potential issues & edge cases in plan. Address proactively. Where could smth go wrong? What about the plan is ambiguous? Missing step, dependency, or pitfall? If any gotchas found, stop & ask up to 3 more questions. (either w/ request_user_input or directly) Refine the plan if any additional useful info is provided. ## Plan Template ```markdown # Plan: [Task Name] **Generated**: [Date] **Estimated Complexity**: [Low/Medium/High] ## Overview [Summary of task and approach] ## Prerequisites - [Dependencies or requirements] - [Tools, libraries, access needed] ## Sprint 1: [Name] **Goal**: [What this accomplishes] **Demo/Validation**: - [How to run/demo] - [What to verify] ### Task 1.1: [Name] - **Location**: [File paths] - **Description**: [What to do] - **Dependencies**: [Previous tasks] - **Acceptance Criteria**: - [Specific criteria] - **Validation**: - [Tests or verification] ### Task 1.2: [Name] [...] ## Sprint 2: [Name] [...] ## Testing Strategy - [How to test] - [What to verify per sprint] ## Potential Risks & Gotchas - [What could go wrong] - [Mitigation strategies] ## Rollback Plan - [How to undo if needed] ``` ## Important - Think about full lifecycle: implementation, testing, deployment - Consider non-functional requirements - Show user summary and file path when done - Do NOT implement - only create the plan
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.