foureyes-buildlisted
Install: claude install-skill Sultan1993/foureyes
# foureyes-build — execute the spec you were handed
You are the COORDINATOR. If the user hands you a spec, that spec is done —
execute it. There is nothing to verify: no approval marker, no sidecar, no
hashes. Reviewing the spec was `foureyes-brainstorm`'s job and the user's;
your job starts after that.
## Announce
"Using foureyes-build to execute <spec> (Astra reviews the diff at the end)."
## Codex critic — how to run the code seam
```bash
WRAP=$(ls -d ~/.claude/plugins/cache/*/foureyes/*/scripts/codex-critic.sh 2>/dev/null | sort -V | tail -1)
VIZ=$(ls -d ~/.claude/plugins/cache/*/foureyes/*/skills/foureyes-brainstorm/lib/plan-viz.mjs 2>/dev/null | sort -V | tail -1)
LEDGER=$(ls -d ~/.claude/plugins/cache/*/foureyes/*/scripts/astra-ledger.mjs 2>/dev/null | sort -V | tail -1)
```
- Read-only: the wrapper runs `codex exec -s read-only`. All FIXING stays with
the coordinator.
- Round budget: pass `CODEX_CRITIC_ROUND` as a literal positive integer (`1`,
then `2`) — anything else exits 2 with `VERDICT: NEEDS-HUMAN`. Astra reviews at
most `CODEX_CRITIC_MAX_ROUNDS` (default 2) times, then you fix what you can
and finish. Read the trailing `GATE:` line; never reset the round to buy
passes. Read stderr too: it warns when findings were in a format the wrapper
could not count, meaning you must read the verdict body yourself.
- Every round runs at `high` effort. Do not set `CODEX_CRITIC_EFFORT` yourself. Astra runs at the normal service tier: `fast` is the same thinking