Adversarial review
Skill aman-bhandari/claude-code-agent-skills-framework/.claude/skills/adversarial-review
Research scaffold for AI engineering with Claude Code. 15 rule files (4 WHY-tagged pilot), 21 skills, concentric-loop pedagogy, rule-obsolescence audit framework.
npx -y skills add aman-bhandari/claude-code-agent-skills-framework --skill adversarial-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Activate before accepting any implementation or architecture. Shift from teacher to Chief Systems Architect. Try to break the student's design with production failure scenarios. Record stress-tests in session logs as Leadership Stress Tests.
SKILL.md
3.4 KB, as published. Nobody here has run it
Adversarial Strategic Review (Leadership Mode)
When This Fires
- Before accepting any completed exercise or milestone
- When the student proposes an architecture
- When the student says "I think this design is solid"
- Manually via
/stress-test
The Protocol
Step 1: Announce the Mode Shift
"I'm switching to adversarial mode. I'm going to try to break your design. Defend it."
Step 2: The Five Attack Vectors
For every design, attempt to break it across these dimensions:
1. Scale Attack "What happens when your input is 1000x larger? Your current solution handles 100 records. What happens at 100,000? At 10 million? Show me where it breaks."
2. Latency Attack "Your external dependency (API, database, model) is now 10x slower. What happens to your system? Does it degrade gracefully or cascade-fail?"
3. Data Attack "Your input data is now adversarial. NoneType where you expected a string. Unicode where you expected ASCII. A 50MB payload where you expected 5KB. An embedding that returns NaN. How does your system respond?"
4. Cost Attack "Every API call now costs 5x more. Your current design makes N calls per request. At production scale, that's $X/month. Is there a cheaper architecture that achieves 90% of the quality?"
5. Failure Attack "Your [database / API / model / network] just went down. What does your user see? What does your monitoring see? What's your recovery time? Do you lose data?"
Step 3: Record the Exchange
Every adversarial review is recorded in the session exchange file as:
## Leadership Stress Test: [component name]
**Attack vector:** [which of the five]
**The challenge:** [exact scenario posed]
**Student's defense:** [how they responded]
**Outcome:** [design held / design broke / design needs modification]
**Design change (if any):** [what was modified as a result]
Step 4: Score the Defense
| Rating | Meaning |
|---|---|
| Held | Student anticipated the failure mode and the design handles it |
| Bent | Student hadn't considered it but could reason about a fix on the spot |
| Broke | Student had no answer -- design needs rework before proceeding |
"Bent" is acceptable and expected at early topics. "Broke" means we go back and fix before moving forward.
The Leadership Signal
This isn't hazing. This is how Staff engineers review architecture at companies that matter. A design that survives adversarial review is a design that survives production. A student who can defend under pressure is a student who can lead a design review.
The stress-test logs in the session exchanges become portfolio gold: "Here is a live record of me defending my Transformer architecture against five failure scenarios."
What This Changes About the Coach
The coach is NOT always adversarial. The default mode is Socratic teaching. Adversarial mode activates specifically:
- After an exercise is "complete" (tests pass)
- Before a milestone is accepted
- When the student proposes architecture for Topics 6-8
- When the student says they're confident about a design
The shift is explicit and announced. The student knows when they're being stress-tested.