stress-testing
Stress-test plans, proposals, and strategies. Use for pre-mortems, assumption audits, risk registers, evaluating business ideas, identifying failure modes, or when you need devil's advocate analysis before committing resources.
npx skills add majiayu000/claude-skill-registry --skill stress-testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Stress Testing Finding the flaws before they find you. ## When to Use - Before committing engineering time - Before choosing a roadmap direction - Before betting on an architecture - When evaluating a business proposal - When something "feels risky" but you can't articulate why ## Process 1. **Summarize the plan** - Neutral wording, 2-4 bullets 2. **Extract assumptions** - What must be true for this to work? 3. **Run pre-mortem** - Imagine failure, work backward 4. **Build risk register** - Likelihood, impact, mitigation 5. **Define kill criteria** - When should we stop? 6. **Propose experiments** - Cheap ways to validate ## Output Contract Structure every stress-test as: ```markdown ## Plan Summary [2-4 bullets, neutral wording] ## Must-Be-True Assumptions | Assumption | How to Verify | Fastest Disproof | |------------|---------------|------------------| | ... | ... | ... | ## Pre-Mortem: It's 1 Year Later, This Failed | Failure Mode | Warning Signal | Prevention | |--------------|----------------|------------| | ... | ... | ... | ## Risk Register | Risk | Likelihood | Impact | Mitigation | Fallback | |------|------------|--------|------------|----------| | ... | H/M/L | H/M/L |
- When to Use
- Process
- Output Contract
- Fundamental Questions
- For Any Idea
- For Claims
- For Plans
- Pre-Mortem Technique
- The Method
- Why It Works
- Questions to Ask
- Common Failure Patterns
- Planning Fallacies
- Assumption Traps
What does the stress-testing skill do?
Stress-test plans, proposals, and strategies. Use for pre-mortems, assumption audits, risk registers, evaluating business ideas, identifying failure modes, or when you need devil's advocate analysis before committing resources.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill stress-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.