A planning tool that turns a feature specification into a written implementation plan and map of file changes.

Use it to decide how a feature should be built, identify affected files, and record the planned approach in plan.md.

It gives you a structured design before code is changed, helping expose architecture and project-context issues early.

afc:plan — Skill for Claude Code by jhlee0409

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add jhlee0409/all-for-claudecode --skill plan

Clone the repo

git clone --depth 1 https://github.com/jhlee0409/all-for-claudecode

Made for: Claude Code.

Or install afc, the plugin that ships this one along with the rest of its 29 skills, 12 agents, 19 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/plan/github.svg)](https://agentmods.dev/skills/jhlee0409/all-for-claudecode/plan)

Your own site

<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/plan"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/plan"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,441 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.02441
Opus 5	$0.00009	$0.01221
Sonnet 5	$0.00004	$0.00488
Haiku 4.5	$0.00002	$0.00244

Measured 9d ago against content hash 75834b179904, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

afc:plan scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

!`cat .claude/afc.config.md 2>/dev/null || echo "[CONFIG NOT FOUND] .claude/afc.config.md not found. Create it with /afc:init."`

skills/plan/SKILL.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/afc:plan — Implementation Design

Generates an implementation plan (plan.md) based on the feature specification (spec.md). Ensures quality with convergence-based Critic Loop and runs research in parallel when needed.

Arguments

$ARGUMENTS — (optional) Additional context or constraints

Project Config (auto-loaded)

!cat .claude/afc.config.md 2>/dev/null || echo "[CONFIG NOT FOUND] .claude/afc.config.md not found. Create it with /afc:init."

Config Load

Always read .claude/afc.config.md first (read manually if not auto-loaded above) — needed for CI Commands (YAML). Architecture, Code Style, and Project Context are auto-loaded via .claude/rules/afc-project.md.

If config file is missing:

Ask the user: ".claude/afc.config.md not found. Run /afc:init to set up the project?"
If user accepts → run /afc:init, then restart this command with the original $ARGUMENTS
If user declines → abort

Execution Steps

1. Load Context

Check current branch → BRANCH_NAME
Find .claude/afc/specs/{feature}/spec.md:
- Search under .claude/afc/specs/ for a directory matching the current branch name or $ARGUMENTS
- If not found: print "spec.md not found. Running /afc:spec to create it first." then execute /afc:spec with $ARGUMENTS. After spec completes, restart this command from the beginning with the original $ARGUMENTS
Read full spec.md
Read .claude/afc/memory/principles.md (if present)
Read CLAUDE.md project context
Memory loading (skip gracefully if directories are empty or absent):
- Quality history: if .claude/afc/memory/quality-history/*.json exists, load the most recent 10 files (sorted by filename descending) and display trend: "Last {N} pipelines: avg critic_fixes {X}, avg ci_failures {Y}". Use trends to inform risk assessment.
- Decisions: if .claude/afc/memory/decisions/ exists, load the most recent 30 files (sorted by filename descending) and check for conflicts with the current feature's design direction.
- Reviews: if .claude/afc/memory/reviews/ exists, load the most recent 15 files (sorted by filename descending) and scan for recurring finding patterns (same file/category appearing in 2+ reviews). Flag as known risk areas.

Read the full file on GitHub · 180 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

plan-template.md 4.8 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 180 lines · 18 tokens per session scan B 75834b179904

Subscribe to this mod's changes

afc:plan is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 2,441 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Planning agentic-coding ai-coding anthropic automation

eval-agents

Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…

FlorianBruniaux/claude-code-ultimate-guide · 93 tokens

afc:plan