stress-test
By oborchers
Adversarial plan review using red-team/blue-team agents -- generates what-if questions and grounds answers in plan artifacts with configurable tool scope
Component Overview
Install
npx claudepluginhub oborchers/fractional-cto --plugin stress-testComponent Details
Commands (1)
Agents (2)
Use this agent to answer what-if questions generated by the red-team agent. The blue team reads the plan, its surrounding artifacts, and the red team's questions, then attempts to answer each one with a grounded verdict. Tool scope is configurable: local artifacts only, with web research, or with system verification. <example> Context: Red team generated 15 what-if questions for an implementation plan. user: "Now have the blue team answer these what-if questions" assistant: "I'll dispatch the blue-team agent to answer each what-if and classify them by verdict." <commentary> The blue team reads the what-if questions and attempts to answer each using the plan, artifacts, and its configured tool scope. Each answer gets a verdict: ANSWERED, PARTIALLY ADDRESSED, NOT COVERED, or UNCERTAIN. </commentary> </example>
Use this agent to generate adversarial what-if questions for a plan document. The red team reads the plan and its surrounding artifacts (codebase, docs, config files) and produces what-if challenges targeting gaps, edge cases, unverified assumptions, and failure modes. It operates strictly on local artifacts -- no web searches or external calls. <example> Context: User wants to stress-test an implementation plan for a new API. user: "Stress-test my implementation plan at ./docs/api-redesign.md" assistant: "I'll dispatch the red-team agent to generate adversarial what-if questions based on your plan and codebase." <commentary> The red-team agent reads the plan and explores the surrounding codebase to generate grounded what-if questions. It does not use web search or external tools. </commentary> </example> <example> Context: User wants to review a business plan with supporting documents. user: "Run a stress test on my go-to-market plan" assistant: "I'll dispatch the red-team agent to challenge the plan against your supporting documents." <commentary> The red-team agent works on any plan type as long as there are local artifacts to reason against. </commentary> </example>
Hooks (1)
README
Similar Plugins
everything-claude-code
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Uses power tools
Uses Bash, Write, or Edit tools