← ClaudeAtlas

fable-harnesslisted

Run an autonomous Opus-Generator + Fable-Verifier harness against a sprint contract with hard ≥98% spec gate, file-based handoff, cron auto-unstick, Monitor on status.txt, read-only approved contracts, session-scoped Stop gate, optional Codex red-team adversary (prompted to BREAK the build), and CronDelete-self on PASS. Use when the user says "fable harness", "fable-harness", "opus builder fable verifier", "opus thinking-high generator", "sprint contract", "spec gate", "hard spec gate", "TDD-driven harness", "Generator + Verifier", "auto-unstick", "go end to end don't ask", "harness this", or "multi-task autonomous build" AND wants the Opus-thinking-high builder / Fable verifier split (use the base `harness-contract` skill instead when the user wants the default Sonnet builder / Opus verifier). Triggers strongly when the request bundles ≥3 deliverables, wants measurable must_pass criteria, no further questions, a hostile Codex red-team gate, and self-termination when the contract is met.
0xAddict/threadwork · ★ 0 · AI & Automation · score 73
Install: claude install-skill 0xAddict/threadwork
# Fable-Harness — Opus-thinking-high Generator + Fable Verifier with Hard Spec Gate A variant of `/harness-contract` (same autonomous Generator + Verifier pattern, same hard spec gate, same hardening) with three deliberate swaps: - **Generator (builder)** runs on **Opus 4.8 with thinking set high** — a deeper, more deliberate builder than the base skill's Sonnet, for work where the implementation reasoning is the hard part. - **Verifier (grader)** runs on **Fable 5** — a fast, cheap, independent grader from a different model family than the builder. That cross-family split preserves the core "never let the implementer grade itself" property while keeping grading turnaround quick. - **`--codex` red-team gate** spawns Codex as a *hostile adversary whose explicit mandate is to FAIL the build* — not the polite skeptic of the base skill. The sprint only earns terminal PASS if Codex genuinely cannot break it. Everything else (contract shape, contract hardening, Stop gate, Monitor/Cron, state machine, evidence layout) is identical to `harness-contract`. 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 s