plan-gap-reviewlisted

# Plan Gap Review Skill Iteratively analyze a document for gaps, contradictions, inconsistencies, and missing pieces. For each gap found, brainstorm 20 solutions and apply the best one. Re-analyze after fixes until clean. ## Step 1: Identify the Document If the user provided a file path as an argument, use that. Otherwise: 1. Check if there's an obvious document in context (e.g., a plan.md being discussed) 2. Look for common plan/spec files: `**/plan.md`, `**/spec.md`, `**/design.md`, `**/ARCHITECTURE.md` 3. If still unclear, use AskUserQuestion to ask: "Which document should I review? Provide the file path." Confirm the document exists and read it. ## Step 2: Run Gap Analysis Spawn an Agent with subagent_type "general-purpose" to analyze the document with fresh eyes. The agent prompt should: - Instruct it to read the ENTIRE document - Look for: contradictions between sections, dangling references, missing cross-references, numbering issues, specification gaps, dead/superseded content, security inconsistencies, UX inconsistencies, ambiguities that block implementation - For each gap, report: number, category (STRUCTURAL/TECHNICAL/SECURITY/UX/CONSISTENCY), severity (CRITICAL/HIGH/MEDIUM/LOW), location, description, and suggested fix - Focus on real problems, not cosmetic nitpicks ## Step 3: Fix Gaps If gaps are found, batch them into groups of 5 and spawn fix agents in parallel. Each fix agent: - Receives the gap descriptions plus the document path - For each gap: b