plan-reviewlisted

# Plan Review — 3-Agent Multi-Perspective Audit Review `.context/plans/` files through 3 independent lenses: **Technical**, **Strategic**, and **Risk**. Each reviewer is a separate subagent with a unique prompt and perspective. The main agent collates results into a consolidated report. This catches what a single reviewer normalises — each subagent brings a fresh set of assumptions and focus areas. ## Prerequisites - A `.context/plans/*.md` file exists to review (or a glob selecting multiple) - The plan has standard YAML frontmatter (`title`, `type`, `status`, `date`) - Your environment supports spawning `general` and `explore` subagent types ## Quick Start ```bash # No CLI commands — this is an agent workflow skill. # Load the skill, then say: "review the plan at .context/plans/<name>.md" ``` ## When to Use - A `.context/plans/*.md` file needs an independent multi-perspective review before implementation - A draft plan needs validation before marking it `ACTIVE` - Multiple plans exist in the same domain and need prioritisation - A stale plan needs a freshness check against current project state - The user explicitly asks for a plan audit ## When NOT to Use - For one-off notes, scratch files, or non-plan documents — use `session-reflection` instead - For plans outside `.context/plans/` — the reviewer prompts assume `.context/` frontmatter conventions - When the plan is trivially small (1 paragraph, no steps) — the overhead of 3 subagents is not justified - When the