Menü
Use when stress-testing design specs. Devil's advocate for assumptions, unknowns, scope.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | stress-testing-specs |
| description | Use when stress-testing design specs. Devil's advocate for assumptions, unknowns, scope. |
∀ complex specs after initial draft. Optional for standard.
¬approve spec until stress-tested. ∀ assumption: challenge explicitly.
## Spec Challenge — [Slice]
### Verdict: APPROVE | REVISE
### Critical Issues (blocks planning)
| # | Section | Issue | Risk |
### Concerns (note in spec, proceed)
| # | Section | Concern | Suggestion |
### Assumptions Verified
- [assumption] — [why holds]
Use when making git commits. Conventional commit format and rules.
Use when running security review on a diff/PR/file. Research-vs-Reporting discipline, three-tier confidence gate, attacker-controllable taxonomy.
Use when invoking plannotator for approval review of generated .tff-cc milestone artifacts (plan, verification, spec).
Use when starting design or discovery work. MUST use before any creative work.
Use when the user wants to report a bug, file an issue, or send feedback about tff-cc. Triggers on phrases like 'report issue', 'file a bug', 'tff-cc broke', 'something is wrong with tff-cc', 'open an issue', '/report-issue'.
Use when creating, refining, or composing skills. Evidence-driven pattern analysis.