Pre-computed context

Current branch: !git branch --show-current 2>/dev/null || echo "unknown" Recent commits: !git log --oneline -5 2>/dev/null || echo "no commits" Working tree status: !git status --porcelain 2>/dev/null | head -10 || echo "clean"

Variables

Arguments: $ARGUMENTS

Purpose

Plans fail when they skip rationale, ignore blast radius, or rush past approval gates. This skill structures the planning step so that every implementation starts with a clear design — with evidence, test strategy, and user sign-off — before a single line of code is written.

This is not Claude Code's built-in plan mode (shift+tab). That is a permission mode — read-only exploration. This skill is a planning discipline — the intellectual work of designing an approach, assessing risks, and getting approval. The two complement each other: use plan mode for safe exploration during planning, and this skill for the structured process around it.

This skill takes the outputs of the earlier stages — exploration (local understanding), research (external evidence), /design (types, contracts, module boundaries, package topology) — and produces a plan the user approves before execution begins.

Philosophy: a 2-minute plan prevents a 20-minute rework cycle. The depth of planning should match the blast radius — a one-file fix gets a brief plan; a cross-cutting architecture change gets a full plan with stress-testing and research-iterate loops.