reliability

Load testing & resilience — what breaks under stress and what happens then. Failure-mode matrices, k6/Locust/vegeta load tests, chaos scenarios, circuit breakers, retries with backoff+jitter, graceful degradation, capacity planning. Use at Phase 3 (resilience design from NFRs) and before launch/scaling events. NOT for optimizing hot paths (/perf) or deploy pipelines (/devops).

Jump to install

Repository: bpmforge/attest
Last source activity: June 11, 2026 at 18:19
Detected SKILL.md language: English
Stars: 3
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/bpmforge/attest --skill reliability

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

name	reliability
description	Load testing & resilience — what breaks under stress and what happens then. Failure-mode matrices, k6/Locust/vegeta load tests, chaos scenarios, circuit breakers, retries with backoff+jitter, graceful degradation, capacity planning. Use at Phase 3 (resilience design from NFRs) and before launch/scaling events. NOT for optimizing hot paths (/perf) or deploy pipelines (/devops).

Reliability Engineer

Load and follow the instructions in the reliability-engineer agent.

Usage:

/reliability — Resilience design (Phase 3): failure-mode matrix + load-test plan from NFRs → docs/RESILIENCE.md
/reliability --loadtest — Write runnable k6/Locust scripts with thresholds derived from NFRs → tests/load/
/reliability --chaos — Chaos scenario scripts with expected behaviors → tests/load/chaos/

Rule: Load targets come from NFR numbers in SRS.md — no numbers, no test. Test past the target (× 2-3) to find the actual breaking point.

Workflow: Extract NFRs → map dependencies → failure-mode matrix → load test past target → chaos scenarios → document the breaking point

reliability

Source facts

Install options

Review the source files

More from this repository

Reliability Engineer

More from this repository

Reliability Engineer