stress-test
Skill1 starsChanged 3 months agoMITView on GitHub
Run a structured decision walkthrough that surfaces every open assumption and dependency in rounds until the plan is fully aligned - before you commit resources or baseline. Use when starting or reshaping a project, clarifying scope, or the user invokes /stress-test.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- arndvs/ctrlshfttheir own version, first seen Oct 15, 2026
- adam-paterson/skillstheir own version, first seen Oct 11, 2026
- shakacode/react_on_railstheir own version, first seen Oct 8, 2026
- sgl-project/rbgtheir own version, first seen Oct 8, 2026
- ai-analyst-lab/ai-analysttheir own version, first seen Sep 10, 2026
- arusli1/askillstheir own version, first seen Sep 2, 2026
Used with
Projects with it also use ai-act-readiness, c-level-agents and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hussain-ElfalahSkillai-act-readiness
Also in 3 projects that use this
- Hussain-ElfalahSkill
c-level-agents
Also in 3 projects that use this
MicrosoftSkillinbox-setup
Set up the Inbox agent with recommended VS Code settings and gh CLI configuration
Also in 3 projects that use this
- +9 more from Hussain-Elfalah
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- shakacode/react_on_rails★ 5.2ksame name
- sgl-project/rbg★ 314same name
- ai-analyst-lab/ai-analyst★ 304same name
- machina-exm/film-studio-skills★ 137same name
- okikusan-public/stock_skills★ 134same name
- gbasin/stress-test-skill★ 44same name
- Hassaan146/claude-skills★ 18same name
- ilya-a11y/growthband-outbound-skills★ 13same name
- erhwenkuo/stock_skills★ 3same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- org-contextSkill
- project-contextSkill
- draft-project-charterSkill
- draft-risk-registerSkill
- draft-scope-statementSkill
- draft-stakeholder-registerSkill
- draft-wbsSkill
- diagnose-project-healthSkill
- recover-projectSkill
- plan-projectSkill
- start-projectSkill
- setup-classic-pmSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Default: ask which mode if unclear.
- Distinctive: line 29
Read existing org/project context (and Decision Log) if present.
- Distinctive: line 31
Ask the whole ready set in one round.
- Distinctive: line 32
Wait for the user’s answers before the next round.
- Distinctive: line 33
Stop when nothing material remains open - the plan is aligned for baseline.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Stress-test
Stress-test is a structured decision walkthrough. It surfaces every open assumption and dependency in rounds until the plan is fully aligned - before you commit resources or baseline.
Modes
- Walkthrough only - sharpen decisions; do not write context files.
- Walkthrough and update documents - same rounds; also update
ORG_CONTEXT.md/PROJECT_CONTEXT.mdand append or bridge the Decision Log as answers land.
Default: ask which mode if unclear. One slash entry: /stress-test.
How to run
- Read existing org/project context (and Decision Log) if present.
- Build the set of open assumptions and dependencies.
- Ask the whole ready set in one round. Number each question. Attach a recommended answer to each.
- Wait for the user’s answers before the next round.
- Stop when nothing material remains open - the plan is aligned for baseline.
Language (required)
| Use | Do not use |
| round | frontier |
| open assumptions and dependencies | grill / grilling / grill-me |
| recommended | BBQ / cooking metaphors |
| document | developer-pack provenance |
Outputs
- Clarified decisions (and optionally updated context documents + Decision Log entries).
- Explicit list of what is now aligned vs still deferred.
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.