claude-hammer

Light planning mode. Use when the user requests a small, clearly-scoped change (roughly ≤3 files, no new interfaces, no ambiguity) that still deserves a written plan before code. For ambiguous or multi-component work, use the forge skill instead. Produces an executable plan with binary acceptance criteria and a self-review, then hands off to hammer.

Strong planning mode. Use when the user requests a non-trivial feature, refactor, or system change — especially when the request is ambiguous, spans multiple files, or says "제대로", "강하게", "빡세게", "thoroughly", "strong plan". Runs deep codebase recon BEFORE asking any question, drafts an executable plan, then requires unanimous approval from a panel of 3+ critic subagents before the plan may be presented. Hooks enforce the critic gate.

Implementation loop. Use when a plan document exists (from forge or blueprint) and implementation should run — including when the user says "implement", "execute the plan", "구현해", "실행해", or approves a plan. Executes tasks through a worker → validator → implementation-critic loop, then a security/QA review gate; any failure loops back to rework. Hooks block turn completion until every task and review passes.