strikelisted

# Strike — One-Shot Fixes (One decisive hammer blow. For work that needs an anvil, not the whole forge.) Strike is a THIN PROFILE over the forge machinery, not a separate system: same dispatch protocol (dispatch.md is binding — briefs, file handoffs, envelope reports, status vocabulary), same `smithy:forger` agent with routed models, same guard grant, and an inspector review. What it skips is the CEREMONY — assay's spec, blueprint's decomposition + persona pass, forge's per-task review loop and TDD selection — never the subagent rules. Read `${CLAUDE_PLUGIN_ROOT}/references/creed.md` and `${CLAUDE_PLUGIN_ROOT}/references/dispatch.md` first (read-once rule applies). 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. Job slug: `strike-<YYYY-MM-DD>` (or the active job when fixing its findings). Log: `bash ${CLAUDE_PLUGIN_ROOT}/scripts/ledger.sh append forge <slug> strike STARTED -` ## When strike — and when NOT | Situation | Lane | |---|---| | Known small changes: review/QA/guild findings, copy fixes, config tweaks, small refactors, obvious bugs WITH known cause | **strike** | | Cause unknown, "why is this broken", intermittent failure | `/smithy:anneal` — strike never guess-fixes | | New behavior/feature, anything spec-shaped | `/smithy:assay` → pipelin