compass-solvelisted
Install: claude install-skill Anselmoo/werkstoff
# compass-solve
Compose the five phases in order. Each phase is a distinct compass skill; this
skill orchestrates them and **enforces the pipeline invariants in code** via the
guard CLI. Never skip a guard call — its non-zero exit is the enforcement.
`GUARD="python3 ${CLAUDE_PLUGIN_ROOT}/scripts/compass.py"`
## Preferred path: the workflow
When the Workflow tool is available, run the whole pipeline through
`${CLAUDE_PLUGIN_ROOT}/workflows/solve.js` (args: `{ task, multipleApproaches?,
requestedBranches?, maxBranchCount?, successCriteria?, priorClarify?, priorExplore? }`).
It computes Kahn waves, enforces phase order, and pauses on blocking uncertainty —
all in code. Prefer it.
**Workflow scripts have no filesystem access**, so every reuse check must happen
before you invoke it — the script runs to completion in one shot; it cannot pause
partway to ask you to look something up.
1. `echo '{"raw_task":"<task>"}' | $GUARD state-find - --output-dir .compass`. If
`found` is true and `state.phase` is `Clarify` or later, that's your
`args.priorClarify` (pass `state.clarify` through unchanged).
2. Only if step 1 found a reusable Clarify run do you already know
`state.clarify.scoped_task` before invoking the workflow — if so, run
`state-find` a second time with that text as `raw_task`. If it finds an
`Explore`-phase match, that's your `args.priorExplore` (pass `state.explore`
through unchanged).
3. If step 1 found nothing, Clarify will run fresh inside the workfl