scenario-scaffolding

Automate ITBench scenario creation by applying faults and generating ground truth DSL.

491|45|Updated Feb 5, 2025
One-click install
npx skills add https://github.com/itbench-hub/ITBench --skill scenario-scaffolding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scenario-scaffolding
Source: https://github.com/itbench-hub/ITBench/tree/main/.claude/skills/sre/scenario-scaffolding
Command: npx skills add https://github.com/itbench-hub/ITBench --skill scenario-scaffolding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assists with end-to-end ITBench scenario creation by automating the complex scaffolding workflow, reducing manual steps and ensuring consistent structure for ground truth formats.

Core Features & Use Cases

  • Automatically identifies target applications, services, and fault injection points.
  • Populates scenario files with disruptions, waitFor hooks, and solutions, then generates groundtruth.yaml and groundtruth_v1.yaml.
  • Validates outputs and prompts regeneration to keep scenarios in sync with ITBench schemas.

Quick Start

Provide the application context and run the scaffolding workflow to generate scenario files.

Frequently Asked Questions about scenario-scaffolding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Kubernetes fault injection scenario creation end-to-end?

Automate Kubernetes fault injection scenario creation by applying disruption mechanisms, mapping propagation, and generating ground truth DSL to produce testable scenarios with minimal manual intervention.

What is groundtruth.yaml schema validation in ITBench scenarios?

Groundtruth.yaml schema validation enforces the groundtruth_v1 and groundtruth.yaml formats and runs make regenerate-scenario-files to keep scenario outputs synchronized with required ITBench schemas.

How do I generate ground truth DSL for fault injection scenarios?

Generate ground truth DSL by coordinating application discovery, service targeting, disruption injections, and alert prediction to populate scenario files with waitFor hooks and solutions.

Does scenario scaffolding work without external dependencies?

Scenario scaffolding operates with no external dependencies, automating application discovery and fault injection internally to populate scenario files and generate valid groundtruth.yaml outputs.

What's the best way to populate ITBench scenario files with disruptions and solutions?

Populate ITBench scenario files by running the scaffolding workflow, which automatically identifies target services, injects disruptions, maps propagation, and writes waitFor hooks and solutions into scenario files.

Why does make regenerate-scenario-files fail during scenario scaffolding?

Regenerate-scenario-files validates scenario outputs against groundtruth_v1 and groundtruth.yaml schemas, failing when generated disruptions, waitFor hooks, or alert predictions do not match required ITBench formats.