planner-implementation-k
How to write implementation plans — code structure, module layout, component connections, with execution blocks at the end
What this skill does
> **Knowledge skill** — Implementation planning: system shape, code structure, interfaces, then execution blocks. # Implementation Planning An implementation plan describes what the code will look like and how the pieces connect. It reads top-down: system first, structure second, execution blocks last. ## Document Flow ``` ┌─────────────────────────────────────────────┐ │ 1. System diagrams │ ← reader sees the whole picture │ Data flows, component layout, │ │ how this fits into existing system │ ├─────────────────────────────────────────────┤ │ 2. Code structure │ ← reader understands what gets built │ Modules, libraries, utilities, │ │ how components connect, key interfaces │ ├─────────────────────────────────────────────┤ │ 3. Key decisions & tradeoffs │ ← reader understands why │ What was chosen, what was rejected, │ │ what remains uncertain │ ├─────────────────────────────────────────────┤ │ 4. Execution blocks (if needed) │ ← reader knows the work │ Verifiable chunks, risk-ordered, │ │ only when plan size warrants it │ └─────────────────────────────────────────────┘ ``` Never invert this. A plan that starts with task breakdowns before showing the system is unreadable. ## System Diagrams Even implementation plans need visuals. Show: - How new code fits into the existing system - Data flow through the implementation - Module/package/component boundaries - Dependency directions These aren't decorative — they're the primary communication. Prose supports diagrams, not the other way around. ## Code Structure The core of an implementation plan. Describe: - What modules exist and what each one does - How components, utilities, and libraries connect - Key interfaces and contracts between pieces - Where new code lives relative to existing code Code snippets are expected but surgical — signatures, type shapes, critical algorithms. Not full implementations. ``` GOOD BAD ──────────────────────────────── ──────────────────────────── Function signatures / type defs Full function implementations Key struct/class shapes Boilerplate setup code Critical algorithm pseudocode Every helper and utility Interface contracts Import statements ``` ## Execution Blocks Not every plan needs these. A clear design with good diagrams and structure may be enough on its own. Add execution blocks when: - The plan is large enough that a builder needs ordering guidance - There are risk points that should be tackled first - Dependencies between pieces create a required sequence - The user asks for them When you do include blocks, each should be: - **Verifiable** — produces something observable, not "service is implemented" - **Right-sized** — meaningful progress, not too granular - **Risk-ordered** — hardest and most uncertain parts first Blocks go at the bottom of the plan. They're an appendix to the design, not the plan itself.
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.