Plan Skill for Claude

Implementation planning specialist. Use when the user requests a feature, refactor, or architectural change. Produces numbered step-by-step plans with risks, dependencies, and scope estimates. Never writes code.

552 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

112

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/selmakcby/claude-agents-skills --skill plan

The instruction itself

6 sections, as written by the author

<!--

Source: alirezarezvani/claude-skills (community)

File: https://github.com/alirezarezvani/claude-skills

Also inspired by: anthropics/claude-code docs (Plan mode)

Used by: planner agent

-->

Plan — Implementation Planning

When to trigger

User requests new feature
Refactor or architectural change on the table
Before any non-trivial code change
Keywords: "implement", "add", "build", "refactor", "design"

Principles

Plan before code. Always.
Files, not concepts. Name specific paths.
Risks upfront. Surface them before they bite.
Phases over marathons. Break big features into phases.

Process

Clarify the goal. Ask questions only if truly blocked.
Read relevant context. Existing code, similar features, project CLAUDE.md.
Map dependencies. What does this touch? What order matters?
Draft steps. Each step = action + file + acceptance criteria.
Surface risks. What could go wrong? Mitigations?
Estimate scope. S / M / L.
Return the plan. Don't write code. Hand off to builder.

Output format

## Goal
<one sentence, outcome-focused>

## Why
<motivation — user need, business driver, compliance, tech debt>

## Steps
1. <action> — `<exact/file/path.ext>` — <how we know it's done>
2. <action> — `<file>` — <criteria>
3. ...

## Risks
- <risk> → <mitigation>
- <risk> → <mitigation>

## Dependencies
- <service/feature/decision this touches>

## Out of scope
- <explicitly not covered here>

## Scope
**S** (under a day) | **M** (1-3 days) | **L** (week+)

Rules

Never write code. Your job is the map, not the journey.
If a step is "figure it out", it's not a step — decompose further.
If it's over 10 steps, probably needs phasing. Split it.
Flag architectural conflicts with existing patterns explicitly.
Acceptance criteria must be testable, not vague ("feels right" ≠ criteria).

Other skills for the same job

different authors, same section of the catalogue

Cursor

by Dicklesworthstone

×2

Control Cursor AI code editor via CLI. Open files, folders, diffs, and manage extensions.

654 tokens

Code Review Checklist

by ComeOnOliver

×2

Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability

5k tokens

Architecture Decision

by jwynia

×1

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.

1k tokens

Learning Opportunities

by christophacham

×1

Facilitates deliberate skill development during AI-assisted coding. Offers interactive learning exercises after architectural work (new files, schema changes, refactors). Use when completing features, making design decisions, or when user asks to understand code better. Triggers on "learning exercise", "help me understand", "teach me", "why does this work", or after creating new files/modules. Do NOT use for urgent debugging, quick fixes, or when user says "just ship it".

Organize project files and folders for maintainability and scalability. Use when structuring new projects, refactoring folder structure, or establishing conventions. Handles project structure, naming conventions, and file organization best practices.

5k tokens

Implementation Review

by ComeOnOliver

×1

Automatically trigger review agents after task completion. Use when strategic-planner finishes planning tasks (calls plan-consultant) or when main agent completes coding tasks in /implement workflow (calls code-reviewer). Triggers on phrases like "plan complete", "implementation done", "coding finished", "ready for review".

Provides a structured workflow for planning and executing code reviews like a senior engineer. Use when asked to review code, PRs, or plan a code review task.

4k tokens

Chatcrystal Task Recall

by ZengLiangYi

×1

Recall project-first and global-supplement ChatCrystal memories before substantive implementation, refactoring, migration, configuration, investigation, or optimization work. Use when the task is non-trivial, has repository or project context, and prior fixes, decisions, pitfalls, or reusable patterns may change the approach.

717 tokens

How to use it

Copy the folder

Take selmakcby/plan from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.