reliability-engineer

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-claude
Last source activity: July 27, 2026 at 19:39
Detected SKILL.md language: English
Stars: 0
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-claude --skill reliability-engineer

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

gauntlet

Gauntlet loop — multi-agent quality harness: a lead sets a real reference bar (a named product, test suite, or baseline to match or beat), splits the goal into gradeable units, builders produce artifacts in clean context, and blind fresh-per-round critics grade each artifact against the bar with evidence; failures loop until every unit passes, two rounds stall, or budget runs out. NOT /challenge (verifies factual claims); NOT /review (one-pass verdict) — this rebuilds until the work beats something real.

2026-08-12

design-iterate

Claude-Design-style visual iteration loop — render the running UI, screenshot at 375/768/1440, critique against docs/design/tokens.json and design principles, apply fixes, re-capture until clean (cap 3 iterations). Also extracts a token baseline from an existing codebase (--sync) and audits real logged-in browsers (--real). NOT a one-pass review — use /ux --review for findings-only; NOT functional conformance — use /ui-verify.

2026-08-10

steward

Project intelligence steward — audits CLAUDE.md / AGENTS.md alignment with actual codebase, captures session learnings, updates project docs. Use after major sessions or when docs feel stale.

2026-07-30

View all from this repository

name	Reliability Engineer
trigger	/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).
agent	reliability-engineer
arguments	[{"name":"--design","description":"Failure-mode matrix + load-test plan (default)","required":false},{"name":"--loadtest","description":"Runnable load-test scripts with NFR-derived thresholds","required":false},{"name":"--chaos","description":"Chaos scenarios as runnable scripts","required":false}]

Triggers the reliability-engineer subagent.

Load testing and resilience — what breaks under stress and what happens then. Timeouts, retries with budgets, circuit breakers, chaos scenarios, k6/Locust plans.

Usage: /reliability (--design default), /reliability --loadtest, /reliability --chaos.

reliability-engineer

Source facts

Install options

Review the source files

More from this repository

More from this repository