smithylisted

# Smithy — Pipeline Orchestrator Read `${CLAUDE_PLUGIN_ROOT}/references/creed.md` and `${CLAUDE_PLUGIN_ROOT}/references/memory.md` first. Resolve memory first: `export SMITHY_MEM="$(bash ${CLAUDE_PLUGIN_ROOT}/scripts/paths.sh mem)"` — every smithy path below is relative to it, and it need NOT be inside the repo. If that dir does not exist, bootstrap per `${CLAUDE_PLUGIN_ROOT}/references/memory.md` § Location. **You orchestrate. You never do phase work yourself.** Each phase runs by invoking that phase's skill; you read back only status lines, artifact paths, and short summaries. Never paste artifact contents into your context. ## Checklist (create a todo per item) 1. Read STATE.md + ledger; resolve resume-vs-new with the user 2. Run each phase via its skill, in state-machine order 3. Gate at every phase boundary (present → ask → log) 4. Route failures through ANNEAL, back to the exact broken unit 5. Exit: TEMPER READY + final gate → STATE.md idle → offer handover ## Process flow ```dot digraph smithy_pipeline { "Read STATE.md + ledger" [shape=box]; "Active job?" [shape=diamond]; "Ask: resume / new / abort" [shape=box]; "ASSAY (/smithy:assay)" [shape=box]; "Gate: spec approved?" [shape=diamond]; "BLUEPRINT (/smithy:blueprint)" [shape=box]; "Gate: plan approved?" [shape=diamond]; "FORGE (/smithy:forge)" [shape=box]; "Task failure x2?" [shape=diamond]; "TEMPER (/smithy:temper)" [shape=box]; "Verdict READY?" [shape=diamond]; "