Plan, run, and learn from deliberate failure-injection exercises — propose a hypothesis, run the experiment in a controlled window, and turn every surprise into a hardening issue.
Reliability and SRE teams practising resilience under controlled failure.
Quick answer
The Chaos game days template is a ready-made workspace for Reliability and SRE teams practising resilience under controlled failure.
Chaos game days template in short
Included when you apply it
Applying this template creates the 1 board below — with every list — and pre-loads 3 sample issues, all yours to edit. The automation rules further down are suggestions you can wire up next; they aren't created for you yet.
A preview of how this template lays out — the boards, their custom workflow states, and where the sample issues land. WIP caps show a badge.
Game days
Kill the primary database replica during peak load
Hypothesis: read traffic fails over within 30s with no data loss.
Inject 300ms latency on the payments dependency
Region evacuation drill — us-east-1 → us-west-2
These rules aren't created when you apply the template — they're recipes you can wire up in Settings → Automations once your board exists.
When
Experiment moves to 'Running'
Then
Page the steady-state observer and start the abort-condition timer
When
Experiment moves to 'Observed'
Then
Generate a findings issue and convert each surprise into a hardening task
Ready to spin this up?
Sign-up takes seconds. We build this template's boards, lists, and sample issues in your new workspace, all yours to edit.
FAQ
Sprint planning
A cycle-driven sprint board with WIP limits, estimates, and PR-linked issues — the default starter pack for product engineering teams.
View templateBug triage
An intake-to-resolution pipeline that separates triage from active fixing, with severity labels and reproduction notes on every card.
View templateRelease checklist
A repeatable release runbook as a sub-issue tree — cut, verify, ship, announce — so nothing ships half-checked.
View template