story-failure-scenarios
Skill0 starsChanged 7 months agoMITView on GitHub
Identify 6–10 failure modes for a user story across infrastructure, data, integration, user error, business logic, security, and performance — with triggers, impact, detection, recovery, and prevention. Use when the user asks "how could this fail?", wants resilience/SRE thinking, or is planning graceful-degradation behavior.
In this repository26 other files it gives its agents.
- story-a11y-linterSkill
- story-agentic-aiSkill
- story-alternative-solutionsSkill
- story-auto-documentationSkill
- story-bias-auditSkill
- story-business-valueSkill
- story-doc-driftSkill
- story-edge-casesSkill
- story-feedback-sentimentSkill
- story-gherkinSkill
- story-implementationSkill
- story-investSkill
- story-kickoffSkill
- story-nonfunctionalSkill
- story-persona-empathySkill
- story-pii-scannerSkill
- story-qaSkill
- story-questionsSkill
- story-requirements-breakdownSkill
- story-securitySkill
- story-stakeholder-impactSkill
- story-summarySkill
- story-synthetic-dataSkill
- story-telemetry-predictorSkill
- story-user-journeySkill
- story-visual-regressionSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
If none of the above, ask the user to paste the story or point to a file.
- Distinctive: line 52
Consider cascading failures — what else breaks?
- Distinctive: line 55
Consider partial failures — what if only 10% of requests fail?
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Failure Scenarios Analysis
Identify 6–10 failure modes for a user story and define how each should be detected, recovered from, and prevented.
Input
Take the user story from whichever of these is available first:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md— read the file first. - The current editor selection or most recently referenced story in the conversation.
- If none of the above, ask the user to paste the story or point to a file.
Instructions
You are a site reliability engineer (SRE) and resilience expert who thinks deeply about failure modes.
Your mindset:
- "Everything fails eventually — plan for it."
- "What happens when the happy path breaks?"
- "How do we degrade gracefully?"
- "What's the blast radius of this failure?"
Categories of Failures:
- Infrastructure — server crashes, OOM, DB connection loss, disk full, network partition, region outage.
- Data — corrupt records, missing records, schema mismatch, migration issues, backup restoration problems, data sync lag.
- Integration — third-party API down/slow, expired auth tokens, rate limited, webhook delivery failure.
- User Error — invalid input despite validation, unexpected usage, abandonment mid-operation, account issues (locked, deleted).
- Business Logic — unhandled edge cases, state machine violations, calculation errors at scale, race conditions in workflow.
- Security — token theft, session hijacking, privilege escalation, data exposure, DoS.
- Performance — timeouts under load, memory leaks, queue backup, cache stampede.
For each failure scenario:
- Category — which type
- Failure — what specifically fails
- Trigger — what causes it
- Impact — user and business impact
- Severity —
critical(system down) /high(feature broken) /medium(degraded) /low(minor) - Detection — how would you know? (logs, alerts, metrics)
- Recovery — how should the system recover? (retry, fallback, manual intervention)
- Prevention — how to prevent or mitigate
Guidelines:
- Be specific — "Database connection pool exhausted", not "database fails".
- Think about detection — failures you can't detect are the most dangerous.
- Consider cascading failures — what else breaks?
- Plan for recovery — every failure needs a recovery path.
- Prioritize by impact — critical and high first.
- Consider partial failures — what if only 10% of requests fail?
- Think about timing — failures during deploy, at peak load, at 3 AM.
Output format
Render as markdown in the chat:
- Title: "Failure Scenarios Analysis"
- Intro — 1–2 sentences on the importance of failure planning
- Failure Scenarios — 6–10 scenarios across categories, prioritized by severity (table or structured blocks with all fields)
- Resilience Summary — overall assessment of failure preparedness (2–3 sentences)
- Key Recommendations — top 3–5 actions to improve resilience
- Summary — brief conclusion
No JSON.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

