forgelisted

# Forge — Implementation Loop Read `${CLAUDE_PLUGIN_ROOT}/references/creed.md`, `${CLAUDE_PLUGIN_ROOT}/references/memory.md`, and `${CLAUDE_PLUGIN_ROOT}/references/dispatch.md` (the dispatch protocol is binding: file handoffs, effort banners, status vocabulary, defensive parsing). Log: `bash ${CLAUDE_PLUGIN_ROOT}/scripts/ledger.sh append forge <slug> loop STARTED -` ## Checklist (create a todo per item) 1. Verify preconditions (plan, briefs, base sha, clean tree) 2. Read ledger; compute resume position 3. Choose implementation mode (TDD vs plain) + resolve the three dials per config 4. Per task: dispatch → handle status → review → verdict → log 5. Parallel batches only: land the integration branch, then merge every lane 6. All tasks DONE + APPROVED; STATE.md updated; hand off to temper ## Preconditions — check all four before any dispatch - `$SMITHY_MEM/jobs/<slug>/plan.md` exists and every task has a brief in `briefs/`. Missing → offer `/smithy:blueprint`; never improvise briefs here. - STATE.md has a base sha (blueprint records it). - Working tree is clean (`git status --short`) — each task commits atomically. Dirty tree → show the user what's dirty and ask; never stash silently. - The plan was approved (gate line in the ledger, or the user says so now). - A commit grant exists (`bash ${CLAUDE_PLUGIN_ROOT}/scripts/guard.sh status`). The orchestrator grants it at the plan gate; running forge standalone, ask the user ("authorize this plan's task commits?") and on