plan-dev

What problem does it solve?

Write development implementation plans before coding. Explores the codebase, understands what exists, identifies reusable patterns and utilities, and produces a concrete plan with exact file paths, code snippets, and verification steps. Use this skill whenever the user asks to "plan", "design a solution", "think through how to", "figure out the approach", "what's the best way to implement", "make a plan", or "implementation plan". Also triggers on "don't code yet", "before we start", "let's think first", "explore first", or architecture reviews. For complex multi-file changes, unfamiliar codebases, or high-risk modifications — plan first, even if the user doesn't explicitly ask. When in doubt, plan before coding.

Core Features & Use Cases

• Generate a concrete, executable implementation plan with exact file paths, function names, and, where appropriate, ready-to-copy code blocks.
• Reuse existing utilities and patterns in the codebase by citing relevant files and touchpoints.
• Deliver the plan as a conversation artifact that guides execution and can be shared across sessions; it is not automatically written to disk unless requested.

Quick Start

Ask me to plan a multi-file change and I will generate a concrete, executable implementation plan you can follow.