loopspeclisted
Install: claude install-skill tommasobbianchi/loopspec
# /loopspec — informal intent → harness-driven delegation specification
Takes everything the user wrote **before** the literal token `/loopspec` and compiles it
into a machine-checkable delegation contract for a DeepSeek worker. The contract's
defining property: **the harness, not the model, decides when the task is done.**
## 1. Trigger & parsing
Input syntax: `<informal task description> /loopspec [flags]`
- Everything preceding `/loopspec` is the requirement source. Text after it is flags only.
- If `/loopspec` appears with nothing before it in the current message, use the most recent
substantive user request in the conversation as the requirement source.
- Never ask clarifying questions before emitting the spec. Ambiguity that survives is
recorded verbatim under **Open Bindings** in §1 of the output and given a stated default.
### Flags
| Flag | Effect |
|---|---|
| `--dispatch` | After emitting the spec, hand it to a DeepSeek worker (see §7). Default: emit only. |
| `--max-iter=N` | Hard iteration ceiling in the convergence loop. Default 6. |
| `--lang=py\|ts\|rs\|go` | Force the toolchain instead of detecting it. |
| `--f2p=<path>` | Name the fail-to-pass test target explicitly. |
| `--dry` | Emit the spec with detected commands but do not run anything, not even detection. |
## 2. Pre-compilation probe (mandatory, cheap, read-only)
The commands in §3 of the output must be **real commands for this repo**, never
placeholders. Before emitting, probe the cwd — o