arbeitsplan-compilelisted

# Compile a problem into a workflow Users are told to "use an agentic workflow" and don't, because the advice is too vague to act on. This skill takes that transformation as its own job: in, a problem in prose; out, a spec concrete enough that a machine runs it and a hook enforces it. **The spec is a coded handoff, not a description.** This repository measured 9 of 11 skill-to-skill chains failing their handoff despite a schema existing upstream; the one that worked copied its predecessor's JSON byte-for-byte into the next dispatch. So every later phase *reads* `workflow.json`. Never paraphrase it into a prompt. ## Steps 1. **Read the schema first** — `references/workflow-spec-schema.md`. It is the authority on every key and on the rejections below. 2. **Decide the problem's shape.** A *change* alters files and can be checked. A *question* wants an answer. **A question is a refusal, not a smaller workflow.** Write an `out-of-scope-reasoning` record naming `compass:compass-solve`, write no phases, and stop. Compiling a swarm for a question produces three confident answers and no way to tell which is right. 3. **Scope it.** If the problem is vague, resolve it with the user before compiling — a spec compiled from a guess is precise about the wrong thing. When `compass` is installed, `compass:compass-clarify-scope` does this well; when it is not, ask directly and say that compass is not installed. Never fabricate compass-shaped output. 4. **Derive