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).

Ir a la instalación

Repositorio: bpmforge/attest
Última actividad en el origen: 11 de junio de 2026 a las 18:19
Idioma detectado de SKILL.md: inglés
Estrellas: 3
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

code

Doc-driven implementation engineer. Reads SDLC design docs first, verifies all library APIs via Context7, then writes clean production code. Enforces anti-slop rules — no over-engineering, no defensive bloat, no hallucinated APIs. Use after design docs exist.

2026-08-17

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

user-guide

Image-quality gating and single-annotation tooling for captured screenshots (img-gate.mjs, annotate.mjs). Placeholder skill front door — T21.2 scope only.

2026-08-10

Ver todos los de este repositorio

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

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Reliability Engineer

Más de este repositorio

Reliability Engineer