Implementation Planner
Use when a coding task is large enough to require repository inspection, a plan, affected files, risks, and verification before implementation.
Install
/plugin marketplace add cellrishi-code/claude-skills-atlasThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add cellrishi-code/claude-skills-atlas --skill implementation-plannergit clone --depth 1 https://github.com/cellrishi-code/claude-skills-atlas.git /tmp/claude-skills-atlas
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-atlas/skills/coding/implementation-planner ~/.claude/skills/implementation-plannerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Implementation Planner ## Goal Turn a coding request into an implementation plan before changing code. ## Instructions 1. Inspect the repository structure and relevant configuration. 2. Identify the smallest set of files likely to change. 3. Trace existing patterns before proposing a new abstraction. 4. State assumptions instead of silently inventing requirements. 5. Produce: - objective - current architecture relevant to the task - files to inspect/change - implementation steps - risks and edge cases - verification plan 6. If important information is missing, ask focused questions before implementation. 7. Do not modify files unless the user explicitly asks for implementation. ## Output Keep the plan concrete enough that another developer can execute it without rediscovering the repository. ## Source note Inspired by recurring community recommendations to separate planning from implementation and keep work focused. See `docs/community-sources.md`. ## Purpose Support users who need to a coding task is large enough to require repository inspection, a plan, affected files, risks, and verification before implementation.. ## When to use Use this skill when the task involves implementation planner and the user needs a structured, repeatable approach. ## Inputs - The user's task, question, or objective. - Relevant source material, data, constraints, and prior decisions. - The required audience, depth, and output format, when specified. ## Outputs
Details
- Skill name
implementation-planner- Repository
- cellrishi-code/claude-skills-atlas
- Path
skills/coding/implementation-planner/SKILL.md- License
- MIT
- Repo updated
- 13 November 2026
FAQ
What does the Implementation Planner skill do?
Use when a coding task is large enough to require repository inspection, a plan, affected files, risks, and verification before implementation.
How do I install the Implementation Planner skill?
Claude Code plugin: /plugin marketplace add cellrishi-code/claude-skills-atlas. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Implementation Planner popular?
It lives in cellrishi-code/claude-skills-atlas, which has 5 GitHub stars and 6 forks.
Related skills
Atlas
5cellrishi-code/claude-skills-atlas
Use the Claude Skills Atlas as a reusable library of skills, prompts, workflows, agents, and templates. Activate when a task can benefit from a pre-made workflow or reusable instruction set.
Codebase Explorer
5cellrishi-code/claude-skills-atlas
Use when entering an unfamiliar codebase and you need to understand architecture, entry points, dependencies, conventions, and data flow before editing.
Codebase Understanding
5cellrishi-code/claude-skills-atlas
Build a reliable mental model of an unfamiliar repository before making changes. Use when entering a new codebase, investigating architecture, or when the user asks where a feature belongs.
Implementation Review
5cellrishi-code/claude-skills-atlas
Review an implementation against its requirements, repository conventions, correctness risks, tests, and maintainability. Use before opening a pull request or when reviewing completed work.
Debug Systematically
5cellrishi-code/claude-skills-atlas
Diagnose software failures systematically instead of guessing. Use for bugs, failing tests, unexpected output, crashes, regressions, and inconsistent behavior.
Adr
9tarunccet/pm-skills
Document architecture and product decisions using the Nygard ADR format — captures context, alternatives considered, and consequences so the team never asks 'why did we do it this way?' again. Use when making architecture decisions, choosing between technical approaches, selecting vendors, or any decision that will be hard to reverse.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.