Help us improve
Share bugs, ideas, or general feedback.
From adversarial-coach
Validates implementation completeness against requirements using adversarial review. Runs a coach-player loop to identify gaps in security, functionality, and test coverage.
npx claudepluginhub agentic-insights/foundry --plugin adversarial-coachHow this skill is triggered — by the user, by Claude, or both
Slash command
/adversarial-coach:adversarial-coachThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides systematic root-cause debugging when tests fail, builds break, or unexpected errors occur. Provides a structured triage checklist to preserve evidence, localize, and fix issues instead of guessing.
Share bugs, ideas, or general feedback.
/coach [requirements-file]
/coach - Infer requirements from context/coach requirements.md - Validate against specific fileYou orchestrate this dialectical loop between implementing agent (player) and reviewer (coach):
/coach invokes adversarial review with independent evaluation of compliance to requirementsIMPLEMENTATION_APPROVED or specific fixesCheck (in order):
requirements.md, REQUIREMENTS.md, SPEC.md, TODO.mdReview 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 |
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. [Specific fix]
Rigorous but fair:
Concise:
Fresh context is your superpower:
IMPLEMENTATION_APPROVED = termination signal
Only use when: all requirements met, code compiles/runs, tests pass, no significant gaps.
If in doubt, don't approve.
User: /coach SPEC.md
Claude:
REQUIREMENTS COMPLIANCE:
- User registration endpoint (bcrypt hashing)
- Login with JWT tokens
- Logout endpoint - not implemented
- Token refresh - missing /auth/refresh endpoint
IMMEDIATE ACTIONS NEEDED:
1. Add POST /auth/logout endpoint
2. Add POST /auth/refresh for token renewal
3. Add tests for 401 on expired tokens
---
User: [fixes] /coach SPEC.md
Claude:
IMPLEMENTATION_APPROVED
- All auth endpoints verified (register, login, logout, refresh)
- 18 tests passing including auth error cases