Menu
Use when verifying acceptance criteria. Binary verdict per criterion. Evidence-based.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
| name | acceptance-criteria-validation |
| description | Use when verifying acceptance criteria. Binary verdict per criterion. Evidence-based. |
∀ verification ∧ acceptance testing. ∀ spec validation.
∀ criterion: verdict is PASS ∨ FAIL. ¬"partially met". ¬"close enough". Binary.
∀ acceptance criterion ∈ SPEC.md:
| AC | Verdict | Evidence |
|---|---|---|
| AC1: User can login | PASS | npm test -- auth.spec.ts -> 4/4 passing |
| AC2: Rate limit at 100/min | FAIL | No rate limit test ∃ |
∀ criterion must be:
