2634 Audit Plans 07684ba6

---
description: Audit implementation plans for completeness
argument-hint: [plan-file-or-folder]
model: opus
---

# Plan Completeness Audit

You are a meticulous implementation planner. Your job is to systematically audit plans for completeness and fill gaps through user interviews.

## Instructions

1. **Discover Plans**
   - If argument provided: Use that specific plan file
   - If no argument: Scan `plans/` folder, fall back to `Development/ROADMAP.md`
   - List all phases found chronologically

2. **For Each Phase (0-10+), Evaluate:**

   Required Criteria (must have):
   - [ ] Acceptance Criteria: Clear, testable success conditions
   - [ ] Implementation Steps: Concrete steps, not just outcomes
   - [ ] Dependencies: Blockers and prerequisites identified

   Recommended Criteria:
   - [ ] Edge Cases: Failure modes, boundary conditions
   - [ ] File Changes: Specific files/modules listed
   - [ ] Test Strategy: Verification approach
   - [ ] Rollback Plan: For production changes

3. **If Phase Has Gaps:**
   - List the specific missing elements
   - Invoke `/interview [plan-file]` to discuss gaps with the user
   - The interview command will ask in-depth questions using AskUserQuestion
   - Document all answers from the interview

4. **Update ALL Related Documentation & Plans After Each Phase:**

   CRITICAL: After resolving gaps in a phase, update ALL affected files—not just the current plan.

   **Documentation:**
   - **ROADMAP.md**: Add key decisions summary, mark with ✅ *Assessed* in phase heading
   - **CLAUDE.md**: Add new roles, principles, anti-goals, or patterns introduced
   - **README.md**: Update if user-facing features or project description changed
   - **.env.local**: Add new API keys or environment variables if introduced
   - **agent_docs/**: Document new features, patterns, or workflows
   - **Database schema docs**: Update if new tables/columns added

   **Related Plans:**
   - **Current plan file**: Add resolved decisions, schema, RLS policies, implementation code
   - **Dependent plans**: If this phase adds schema/features that later phases reference, update those plans
   - **Foundation plan**: If core patterns change, update foundation-phases docs
   - **Cross-cutting concerns**: If auth, roles, or permissions change, update all affected phase plans

5. **Track Progress:**
   ```
   Audit Progress:
   - [x] Phase 0: Complete
   - [ ] Phase 1: In Progress
   - [ ] Phase 2: Pending
   ```

6. **Repeat** until all phases audited

## Evaluation Scoring

- **Complete** (3/3 required + 2+ recommended): Proceed to next
- **Needs Work** (2/3 required): Quick clarification via AskUserQuestion
- **Incomplete** (0-1/3 required): Deep dive via /interview

## Begin

Start by discovering plans in the current project. Read `$1` if provided, otherwise scan for plan files.