Rubber Duck Reviewer

Invoke a separate, stateless subagent to independently critique your plan or implementation before proceeding. This catches blind spots, logic errors, and security issues while course corrections are still cheap.

Most non-trivial tasks that fail had issues a rubber-duck critique could have caught early. Treat this as a required step for non-trivial work, not an optional enhancement.

When to Invoke

Always invoke before implementing when:

• Plan touches more than one file
• Plan involves database schema changes, API contracts, or security-sensitive logic
• Making an architectural decision with long-term consequences
• Uncertain about an assumption

Invoke after completing a unit of work when:

• Finished implementing a module, endpoint, or feature
• Wrote tests and want to validate coverage of critical paths
• Refactored non-trivially