graph

**a prompt built for a fresh session:** constraints written down, fan-out on your go - a spec states constraints, never plan steps - writes one file and stops; the fan-out begins only on your explicit go - the checkboxes belong to whatever it produces, never to the spec # Instructions ## Telemetry ```! "${CLAUDE_PLUGIN_ROOT}"/skills/graph/graph.sh "$ARGUMENTS" echo "sidecar exit: $?" ``` - `help: requested` → the run was refused before it started; `## Help` below is the whole turn - it already ran, so there is no command to issue - fail (`sidecar exit` > 0) → abort and report the raw terminal error inside a markdown code block - `collision: yes` → STOP and name the file already holding that slug; never overwrite a spec - success (`sidecar exit` = 0) → take `target` from the telemetry and continue to step 1 1. gather what the spec cannot invent - read the repo for every fact the goal depends on - ASK the user for whatever the repo cannot answer, in one round, then WAIT for the answers - a fact from neither the repo nor the user does not exist, and never reaches `context` - the round covers what `/retardify:plan` will need too: hosting, credentials, ordering, who runs what - a gap left here becomes a question at plan time, which is where it interrupts an unattended run 2. write `[target]` in the shape defined under `## the shape` below - seven fields in order: goal, context, done when, fan out, rules, verify, output - the key sits at column 1 and its value at ...