Stress Test

Adversarially stress-test a technical plan by verifying claims against real docs, running POC code, and updating the plan before you build.

45 stars 1 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add gbasin/stress-test-skill

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add gbasin/stress-test-skill --skill stress-test
Manual install
git clone --depth 1 https://github.com/gbasin/stress-test-skill.git /tmp/stress-test-skill
mkdir -p ~/.claude/skills
cp -r /tmp/stress-test-skill/skills/stress-test ~/.claude/skills/stress-test

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Stress-Test Plan

You are an adversarial reviewer. Optimize for reducing pre-build uncertainty, not for reaching a recommendation quickly. Spend extra effort on assumptions whose failure would cause outage, data loss, security issues, expensive rework, or misleading confidence.

Challenge the plan until each critical claim is either evidenced, tested, or explicitly accepted as a risk. Be direct and specific.

Maintain a compact proof table for critical claims:
- **Claim**
- **Impact if false**
- **Strongest evidence**
- **Contradictory or missing evidence**
- **Status**: `docs-confirmed`, `code-confirmed`, `POC-confirmed`, `contradicted`, or `unresolved`
- **Next action**

Only create `.poc-stress-test/` if at least one POC is approved. All POC work MUST happen inside it, and it must be cleaned up at the end.

## Phase 1: Extract & Decompose

Read back the plan from the conversation. Break it into:
- **Decisions**: Every concrete technical choice (library, pattern, protocol, data model, etc.)
- **Assumptions**: Things stated as fact but not verified ("library X supports Y", "this scales to Z")
- **Dependencies**: External things the plan relies on (APIs, packages, services, OS features)
- **Interfaces**: Boundaries between components where things can go wrong
- **Ordering**: Implicit sequencing — what must happen before what
- **Invariants**: Conditions the plan depends on staying true over time
Read the full skill on GitHub

Details

Skill name
stress-test
Path
skills/stress-test/SKILL.md
License
MIT
Repo updated
23 March 2026

FAQ

What does the Stress Test skill do?

Adversarially stress-test a technical plan by verifying claims against real docs, running POC code, and updating the plan before you build.

How do I install the Stress Test skill?

Claude Code plugin: /plugin marketplace add gbasin/stress-test-skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Stress Test popular?

It lives in gbasin/stress-test-skill, which has 45 GitHub stars and 1 forks.

Related skills

Drupal Testing

84

grasmash/drupal-claude-skills

Test-driven development for Drupal with PHPUnit and Drupal Test Traits (DTT). Use when writing or fixing tests, deciding what is worth a test, reproducing a bug before fixing it, choosing a bootstrap level (Unit vs Kernel vs ExistingSite/functional), testing permission gates, adding Playwright visual verification, or debugging tests that silently run zero assertions. Covers the bug-fix RED-first discipline, the worth-a-test rubric, bootstrap cost tradeoffs, negative tests, the anonymous-403 permission trap, DTT gotchas, and the PHPUnit-version pin that makes Drupal tests pass vacuously.

Testing & QA

Playwright QA CLI

58

EricTechPro/startup-claude-skills

Automated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific fea

Testing & QA18

Test Audit

49

PyModel/jev-judge-mcp

Invoke whenever writing, changing, reviewing, or sweeping tests in jev-judge-mcp. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand, under this repo's rule that a test is never deleted or weakened to make a failing build pass.

Testing & QA

Fix Ticket

58

EricTechPro/startup-claude-skills

Automate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.

Testing & QA18

Olore Bunit Latest

119

olorehq/olore

Local bunit documentation reference (latest). bUnit Blazor testing documentation. Use for Blazor component testing, rendering, event handling, JSInterop mocking, and test assertions in .NET.

Testing & QA

Owasp AI Testing

74

mastepanoski/claude-skills

AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.