/pressure-test-this

Subject a technical design, architecture, RFC, state machine, API contract, or implementation plan to adversarial real-world stress before code is written.

Run the phases in order. Findings are provisional until they pass Phase 2. Every survivor must carry a structural hardening fix.

Lineage & Core Philosophy

This skill fuses the adversarial refutation rigor of antimatter-code-quality-review with the upstream prevention discipline of correct-by-construction and pizza1.

• Zero severity theater: Speculative "what-ifs" and generic edge-case doom-mongering are prohibited. A fracture is reported only if you can demonstrate the exact sequence of events or inputs that breaks an invariant under real domain constraints. Everything else is destroyed before output.
• Zero verdict theater: No report-card badges (BLOCKS IMPLEMENTATION, Score: 7/10, Fatal Cracks: 2). The reader needs to know what to do and why, not an arbitrary grade.
• Clean approval is a first-class outcome: When a design withstands all vectors without structural cracks, approve it directly. Manufacturing flaws to look thorough is a failure of this skill.
• Correctness over convention: Never defend or critique a design by pointing to what the codebase already does, what is conventional, or what creates the least diff.