adversarial-coach

---
name: adversarial-coach
description: Adversarial implementation review based on Block's g3 dialectical autocoding research. Use when validating implementation completeness against requirements with fresh objectivity.
---

# /coach - Adversarial Implementation Review

## Usage

```
/coach [requirements-file]
```

- `/coach` - Infer requirements from context
- `/coach requirements.md` - Validate against specific file

## Coach-Player Loop

You orchestrate this dialectical loop between implementing agent (player) and reviewer (coach):

1. You (player) implement features
2. `/coach` invokes adversarial review with independent evaluation of compliance to requirements
3. Coach returns: `IMPLEMENTATION_APPROVED` or specific fixes
4. Address feedback, loop until approved

## Review Process

### Step 1: Identify Requirements

Check (in order):
- Specified requirements file or issue/ticket mentioned
- `requirements.md`, `REQUIREMENTS.md`, `SPEC.md`, `TODO.md`
- Conversation context; ask user if nothing found

### Step 2: Adversarial Review

Review with **fresh objectivity** - discard prior knowledge, don't rationalize shortcuts.

| Check Category | Items |
|----------------|-------|
| Requirements | Each item: implemented or missing with specific gap |
| Compilation | Compiles? Tests pass? Runs? |
| Common Gaps | Auth on endpoints, token refresh endpoint, HTTPS, bcrypt for passwords, error handling, input validation |
| Functional | Test actual flows (not just compilation), verify edge cases work |
| Test Coverage | Auth error cases (401/403), token expiry, invalid inputs, rate limits |

### Step 3: Return Verdict

**If approved (>95% complete):**
```
IMPLEMENTATION_APPROVED

- [Requirement 1]: Verified
- [Requirement 2]: Verified
- Compilation: Success
- Tests: All passing
```

**If fixes needed:**
```
REQUIREMENTS COMPLIANCE:
- [Requirement]: Implemented
- [Requirement]: Missing - [specific gap]

IMMEDIATE ACTIONS NEEDED:
1. [Specific fix with file/line if known]
2. [Sp