ExcelAIQ-Bank

Use when the user submits a new feature request or complex change that needs structured clarification before design. Not for simple bug fixes, config changes, or minor edits that can go directly to implementation.

Use after requirement clarification is complete, to produce a technical design document before any code is written. Not for simple tasks that don't need architecture planning.

Use when technical design is complete and approved, to produce a bite-sized implementation plan with exact file paths, code, and commands.

Use when worker has completed implementation and code needs systematic review before proceeding. Works for both same-model and cross-model review.

Use after docs-reviewer has completed compliance review, to perform adversarial/critical review of design or plan documents. Focuses on questioning decisions, finding blind spots, and checking edge cases that compliance review misses.

Use when a design document or implementation plan has been produced and needs compliance review before adversarial review. Checks coverage, consistency, feasibility against upstream documents.