harness-contractlisted

# Harness-Contract — Autonomous Generator + Verifier with Hard Spec Gate A specialisation of the base `/harness` Generator-Verifier pattern (which assumes one open-ended app build). This skill is for **bounded, multi-deliverable work** where: - You can write a closed set of must_pass acceptance criteria - Each criterion has a literal shell command that proves PASS/FAIL - The contract is locked before spawning agents (no scope negotiation mid-flight) - The work terminates *itself* on contract completion (no human checkpoints) - The approved contract is made read-only and hash-checked before agents start - A session-scoped Stop hook blocks final stop until terminal PASS evidence is real The output is a sprint that runs to PASS or escalates cleanly at a tick budget — no infinite loops, no ambiguous "done". ## Mode flags - `--codex-verify` (alias `--codex`): add a third **red-team** gate using Codex MCP before terminal completion. The Codex agent is not a neutral second opinion — it is told its job is to **make the spec gate fail**: find any deliverable that doesn't truly work, any fabricated evidence, any hollow PASS. The Stop hook does not call MCP itself; it blocks stop until `{SPRINT_DIR}/codex-adversarial-report.md` exists and contains `ADVERSARIAL PASS` (the verdict Codex is only allowed to write when it tried to break the build and genuinely could not). ## When to use vs when to skip **Use** when the user wants: - 2+ coordinated deliverables (e.g. config edit + memo