/coach - Adversarial Implementation Review

Usage

CODEBLOCK0

• - /coach - Infer requirements from context
• INLINECODE1 - Validate against specific file

Coach-Player Loop

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

1. 1. You (player) implement features
2. INLINECODE2 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
• INLINECODE4, REQUIREMENTS.md, SPEC.md, INLINECODE7
• 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):
CODEBLOCK1

If fixes needed:
CODEBLOCK2

Key Principles

Rigorous but fair:

• - Catch real gaps (security, logic, data flow), not style preferences
• Functionality over aesthetics; always flag security issues (auth, crypto, validation)

Concise:

• - Bullets, not essays; specific issues, not vague concerns
• No file contents or verbose analysis in output

Fresh context is your superpower:

• - Review as if you've never seen this code; validate against requirements, not intentions

Magic Signal

INLINECODE8 = termination signal

Only use when: all requirements met, code compiles/runs, tests pass, no significant gaps.

If in doubt, don't approve.

Minimal Example

CODEBLOCK3

Research

• - Paper: Adversarial Cooperation in Code Synthesis
• Implementation: g3
• Key insight: Discard implementing agent's self-report; perform independent evaluation against requirements.