Rehearse the bad day before it happens.
Free & open · no signup · read-only — every stage ends by asking · nothing leaves your machine
Whether it survives a bad day: graceful degradation when a dependency dies, the failure experiments worth running, the first bottleneck under load, abuse defenses, and incident readiness.
The conductor fetches each brief in turn and writes its report before moving on — later briefs can build on earlier findings. Or copy any single stage to run it alone.
5 reports in reports/, plus the run's own INDEX.md: DEGRADE.md, CHAOS.md, CAPACITY.md, ABUSE.md, RELIABILITY.md. Feed them to the optional Studio to turn findings into commits, or run 28 · Roadmap Synthesis to merge them into one plan.
Copy the conductor into your agent inside the repo you want checked. It runs each Goal Prompt in sequence, honoring each one's ask-first rule.
What happens when a dependency is slow or down — whether the product degrades gracefully with timeouts, fallbacks, and breakers, or cascades into a full outage.
Kill every dependency on paper — trace the actual catch, timeout, and fallback code, or its absence — and script the game day before production improvises one.
Every ceiling the config actually sets — pools, workers, queue bounds — read into a headroom ledger naming what saturates first, and at what multiple of today.
Whether the system defends itself against traffic that is not a well-behaved user — bots, scrapers, floods, and expensive requests that can exhaust it.
The 3am table — for each failure scenario: how you'd detect it, how you'd respond, and the gap in between.