Validates AI implementation plans before execution. Use when user says "check your plan", "validate this plan", "review the plan", or "is this plan good"...
Validate AI-generated implementation plans before execution to catch hallucinations, pattern violations, and scope creep.
Invoke when user says:
Different from check-your-code/work: check-your-code and check-your-work review written code. check-your-plan reviews the PLAN before code is written.
| Phase | Agents | Action |
|---|---|---|
| 1 | - | Plan Discovery (locate plan, extract content) |
| 2 | 5 parallel | Plan Validation (specialized reviewers) |
| 3 | 1 | Devil's Advocate (challenge all findings) |
| 4 | - | Report + User Decision |
For Phase 2 details: references/phase-2-plan-validators.md For Phase 3 details: references/phase-3-devil-advocate.md For report format: templates/plan-assessment.md
| Agent | Focus |
|---|---|
| completeness-checker | All requirements addressed? 70% problem? Vague steps? |
| pattern-compliance-checker | CLAUDE.md rules? TanStack Query? Zod? File conventions? |
| feasibility-checker | Hallucinated APIs? Real file paths? Valid dependencies? |
| risk-assessor | Security gaps? Missing error handling? Rollback plan? |
| scope-discipline-checker | Over-engineering? Scope creep? Simplest solution? |
| Agent | Focus |
|---|---|
| devil-advocate | Challenge all findings, reduce false positives |
| Level | Meaning | Example |
|---|---|---|
| P0 | Plan will fail | Hallucinated API, wrong file path, missing dep |
| P1 | Major pattern violation | useState+service, handwritten interface, no org_id |
| P2 | Could be better | Minor pattern deviation, missing edge case |
| P3 | Suggestion | Over-engineering detected, style preference |
P0 requires evidence: "File X doesn't exist" not just "might be wrong"
| Gate | Phase | Question |
|---|---|---|
| Scope | 1 | "Review this plan?" (if plan >50 lines) |
| Action | 4 | "Revise plan / Proceed as-is / Start over?" |
Locate the plan to validate:
.claude/plans/ for recent plan filesExtract plan content and metadata:
If plan >50 lines, use AskUserQuestion to confirm scope
Launch ALL 5 agents in a single message with multiple Task calls. See references/phase-2-plan-validators.md for agent prompts.
Provide each agent:
Launch 1 agent to challenge ALL findings from Phase 2. See references/phase-3-devil-advocate.md for agent prompt.
Provide:
Output: Validated findings with status (CONFIRMED/DOWNGRADED/DISMISSED/UPGRADED)
{
questions: [
{
question: "How would you like to proceed with this plan?",
header: "Action",
options: [
{
label: "Revise plan",
description:
"Update plan to address P0/P1 findings before implementing",
},
{
label: "Proceed as-is",
description: "Accept the plan and start implementation",
},
{
label: "Start over",
description: "Request a completely new plan approach",
},
],
multiSelect: false,
},
];
}
src/types/forms/ (not handwritten interfaces)mutateAsync in modal forms (not mutate())contactFilters.ts for contact filtering (not inline filters)notifyApi for notifications (not direct useToast)organization_id filter on all queriesFor comprehensive quality: check-your-plan (before) + check-your-code + check-your-work (after)
Pattern files checked for compliance:
CLAUDE.mdtanstack-query-patterns.mdzod-form-patterns.mdreact-typescript-antipatterns.mdmodal-form-patterns.mdnotification-patterns.mdsettings-patterns.mdCommon P0 findings:
src/services/foo.ts doesn't existuseAccounts() hook doesn't existCommon P1 findings:
v1.1.0 (2025-01-18): AI optimization updates
v1.0.0 (2025-01-12): Initial release