designing-distributed-system-tests

SKILLWorkflowcommunity
v0.0.0shenliMITUpdated 25d agoSource →

Use when designing a test plan for a distributed or stateful system — anything with persistence, replication, consensus, retries, idempotency, async messaging, multi-tenancy, or partial failure. Plans are claim-driven: investigate the product's claimed guarantees first, then design hypotheses and sc

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
228Repo stars
1Clients
1Formats
25d agoLast update
Skill
Authorshenli
Version0.0.0
LicenseMIT
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor
Copilot
ChatGPT
Gemini
About

Use when designing a test plan for a distributed or stateful system — anything with persistence, replication, consensus, retries, idempotency, async messaging, multi-tenancy, or partial failure. Plans are claim-driven: investigate the product's claimed guarantees first, then design hypotheses and scenarios that try to falsify those claims under fault. Handles change-scoped plans (a commit / PR / f

Keywords
skillclaude