How does this skill help with safety during chaos testing?

It provides structured templates for defining abort conditions, kill switches, and rollback plans to ensure that exercises can be stopped immediately if they negatively impact production.

What is the difference between a GameDay and Chaos Engineering?

A GameDay is a scheduled, manual team exercise focused on practice and coordination, whereas Chaos Engineering typically involves continuous, automated experiments.

What is a GameDay exercise?

A GameDay is a scheduled, controlled drill where teams simulate system failures to test resilience, monitoring, and incident response procedures in a safe environment.

Can I use this for cloud-native disaster recovery?

Yes, it includes specific scenarios for infrastructure failures, network partitions, and database failovers common in AWS, GCP, and Azure environments.

GameDay Planning

Name: GameDay Planning
Author: melodic-software

bymelodic-software

•

Security & Testing

Facilitates the planning, execution, and analysis of GameDay exercises to strengthen system resilience and incident response readiness.

About

The GameDay Planning skill provides a comprehensive framework for orchestrating scheduled chaos experiments and infrastructure fire drills. It guides teams through every stage of the resilience-testing process—from defining SMART objectives and designing specific failure scenarios to managing real-time execution and conducting thorough postmortems. By providing templates for scenario design, safety 'kill switches,' and role assignments, this skill ensures that teams can test their systems' reliability in a controlled, productive manner that translates into actionable improvements for production stability.

Key Features

Role definition guides for leads, executors, observers, and scribes.
12 GitHub stars
Structured planning timelines covering four weeks of preparation and execution.
Comprehensive safety guidelines including kill switches and abort protocols.
Post-exercise debriefing and formal postmortem reporting frameworks.
Detailed failure scenario templates for infrastructure, application, and data layers.

Use Cases

Identifying hidden dependencies and single points of failure in distributed systems.
Designing complex failover scenarios to validate disaster recovery plans.
Training incident response teams on new architectures through controlled chaos drills.

About

Key Features

Role definition guides for leads, executors, observers, and scribes.
12 GitHub stars
Structured planning timelines covering four weeks of preparation and execution.
Comprehensive safety guidelines including kill switches and abort protocols.
Post-exercise debriefing and formal postmortem reporting frameworks.
Detailed failure scenario templates for infrastructure, application, and data layers.

Use Cases

Identifying hidden dependencies and single points of failure in distributed systems.
Designing complex failover scenarios to validate disaster recovery plans.
Training incident response teams on new architectures through controlled chaos drills.