plan

Name: plan
Author: selmakcby

111stars17forks

How to install plan?

selmakcby/claude-agents-skills/plan

$npx -y skills add selmakcby/claude-agents-skills --skill plan

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	<!--
2	Source: alirezarezvani/claude-skills (community)
3	File: https://github.com/alirezarezvani/claude-skills
4	Also inspired by: anthropics/claude-code docs (Plan mode)
5	Used by: planner agent
6	-->
7
8	# Plan — Implementation Planning
9
10	## When to trigger
11	- User requests new feature
12	- Refactor or architectural change on the table
13	- Before any non-trivial code change
14	- Keywords: "implement", "add", "build", "refactor", "design"
15
16	## Principles
17
18	- Plan before code. Always.
19	- Files, not concepts. Name specific paths.
20	- Risks upfront. Surface them before they bite.
21	- Phases over marathons. Break big features into phases.
22
23	## Process
24
25	1. Clarify the goal. Ask questions only if truly blocked.
26	2. Read relevant context. Existing code, similar features, project CLAUDE.md.
27	3. Map dependencies. What does this touch? What order matters?
28	4. Draft steps. Each step = action + file + acceptance criteria.
29	5. Surface risks. What could go wrong? Mitigations?
30	6. Estimate scope. S / M / L.
31	7. Return the plan. Don't write code. Hand off to builder.
32
33	## Output format
34
35	```markdown
36	## Goal
37	<one sentence, outcome-focused>
38
39	## Why
40	<motivation — user need, business driver, compliance, tech debt>
41
42	## Steps
43	1. <action> — `<exact/file/path.ext>` — <how we know it's done>
44	2. <action> — `<file>` — <criteria>
45	3. ...
46
47	## Risks
48	- <risk> → <mitigation>
49	- <risk> → <mitigation>
50
51	## Dependencies
52	- <service/feature/decision this touches>
53
54	## Out of scope
55	- <explicitly not covered here>
56
57	## Scope
58	S (under a day) \| M (1-3 days) \| L (week+)
59	```
60
61	## Rules
62
63	- Never write code. Your job is the map, not the journey.
64	- If a step is "figure it out", it's not a step — decompose further.
65	- If it's over 10 steps, probably needs phasing. Split it.
66	- Flag architectural conflicts with existing patterns explicitly.
67	- Acceptance criteria must be testable, not vague ("feels right" ≠ criteria).

People who liked this also viewed

6 picks

Type

plan

111stars17forks

View on GitHub

How to install plan?

selmakcby/claude-agents-skills/plan

$npx -y skills add selmakcby/claude-agents-skills --skill plan

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!--
2	Source: alirezarezvani/claude-skills (community)
3	File: https://github.com/alirezarezvani/claude-skills
4	Also inspired by: anthropics/claude-code docs (Plan mode)
5	Used by: planner agent
6	-->
7
8	# Plan — Implementation Planning
9
10	## When to trigger
11	- User requests new feature
12	- Refactor or architectural change on the table
13	- Before any non-trivial code change
14	- Keywords: "implement", "add", "build", "refactor", "design"
15
16	## Principles
17
18	- Plan before code. Always.
19	- Files, not concepts. Name specific paths.
20	- Risks upfront. Surface them before they bite.
21	- Phases over marathons. Break big features into phases.
22
23	## Process
24
25	1. Clarify the goal. Ask questions only if truly blocked.
26	2. Read relevant context. Existing code, similar features, project CLAUDE.md.
27	3. Map dependencies. What does this touch? What order matters?
28	4. Draft steps. Each step = action + file + acceptance criteria.
29	5. Surface risks. What could go wrong? Mitigations?
30	6. Estimate scope. S / M / L.
31	7. Return the plan. Don't write code. Hand off to builder.
32
33	## Output format
34
35	```markdown
36	## Goal
37	<one sentence, outcome-focused>
38
39	## Why
40	<motivation — user need, business driver, compliance, tech debt>
41
42	## Steps
43	1. <action> — `<exact/file/path.ext>` — <how we know it's done>
44	2. <action> — `<file>` — <criteria>
45	3. ...
46
47	## Risks
48	- <risk> → <mitigation>
49	- <risk> → <mitigation>
50
51	## Dependencies
52	- <service/feature/decision this touches>
53
54	## Out of scope
55	- <explicitly not covered here>
56
57	## Scope
58	S (under a day) \| M (1-3 days) \| L (week+)
59	```
60
61	## Rules
62
63	- Never write code. Your job is the map, not the journey.
64	- If a step is "figure it out", it's not a step — decompose further.
65	- If it's over 10 steps, probably needs phasing. Split it.
66	- Flag architectural conflicts with existing patterns explicitly.
67	- Acceptance criteria must be testable, not vague ("feels right" ≠ criteria).

People who liked this also viewed

6 picks

Type