Generate executable implementation plans with exact file paths and code blocks.
npx skills add https://github.com/Planxnx/skills --skill plan-dev
Please help me install this Agent Skill. Skill: plan-dev Source: https://github.com/Planxnx/skills/tree/main/skills/plan-dev Command: npx skills add https://github.com/Planxnx/skills --skill plan-dev
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.
Ask me to plan a multi-file change and I will generate a concrete, executable implementation plan you can follow.
High-intent search queries and answers about installing and using this skill.
An implementation plan for unfamiliar codebases should identify relevant files, reusable patterns, and existing utilities. It must specify exact file paths, function names, and ready-to-copy code blocks to ensure modifications are executable and verifiable.
The best way to figure out the approach for high-risk modifications is to perform an architecture review of the codebase first. This identifies reusable patterns and existing utilities, producing a concrete plan with exact file paths and verification steps before any coding begins.
You need to generate an implementation plan before writing code when dealing with complex multi-file changes, unfamiliar codebases, or high-risk modifications. Planning first is necessary to identify relevant files, reusable patterns, and exact file paths for safe execution.
No, the implementation plan does not automatically write code snippets to disk. It is delivered as a conversation artifact containing exact file paths and ready-to-copy code blocks to guide execution, and it is not written to disk unless explicitly requested.
To ensure verification steps are included in a codebase architecture plan, generate the plan by analyzing existing code patterns and utilities. The resulting implementation plan will specify exact file paths, function names, and ready-to-copy code blocks alongside necessary verification steps.
mehdicScan repository contents to detect patterns and extract reusable utilities.
BrunoAMSilvaGenerate implementation documentation with file paths, code blocks, and validation checklists from a master plan.md file.
ngocsangyemMap files, entry points, and architectural patterns across directories with parallel Explore subagents.
vathymutConvert high-level specifications and tickets into executable code.
