review-plan

<skill name="apex:review-plan" phase="advisory">

<overview>
Lightweight plan review that catches gaps and errors before implementation commitment.

Three focused lenses:
1. **Completeness** - Are all required plan artifacts present and substantive?
2. **Gap Analysis** - What did research find that plan doesn't address?
3. **Correctness** - Is the plan internally consistent and feasible?

Output goes to chat. User fixes issues inline, then proceeds to implement.
</overview>

<phase-gate requires="none" sets="none">
  <reads-file>./.apex/tasks/[ID].md</reads-file>
  <expects-sections>research, plan</expects-sections>
  <outputs-to>chat</outputs-to>
</phase-gate>

<principles>
- **Advisory Only**: No phase changes, no file modifications
- **Fast**: Direct analysis, no subagents
- **Actionable**: Every gap or error includes what to fix
- **Honest**: Call out real problems, don't rubber-stamp
- **Flexible**: Works regardless of current phase
</principles>

<initial-response>
<if-no-arguments>
I'll review the plan for gaps and correctness. Please provide the task identifier.

You can find tasks in `./.apex/tasks/` or run with:
`/apex:review-plan [identifier]`
</if-no-arguments>
<if-arguments>Load task file and begin review.</if-arguments>
</initial-response>

<workflow>

<step id="1" title="Load task and extract sections">
<instructions>
1. Read `./.apex/tasks/[identifier].md`
2. Note current phase from frontmatter (informational only - don't block)
3. Extract and parse (note any missing sections):
   - `<task-contract>` - From within `<research>` section
   - `<research>` - All findings from research phase
   - `<plan>` - All artifacts from plan phase
4. If `<research>` or `<plan>` sections are missing/empty, report as finding (don't refuse)
5. Verify file paths mentioned in `<plan><architecture-decision><files-to-modify>` exist using glob/ls
</instructions>
</step>

<step id="2" title="Completeness Check">
<purpose>
Verify all mandatory plan artifacts are present and s