request-reviewlisted

# Request Review Dispatch a fresh reviewer agent with a clean context. The reviewer has no shared state — it can give a genuine second opinion because it hasn't been involved in writing the code. **Distinct from `audit-code`:** `audit-code` is the coding agent checking its own work (internal). This skill dispatches an external agent whose job is to find what the coding agent missed. **Solo developer note:** This replaces the human reviewer. The reviewer agent IS the reviewer. **Run `audit-code` first.** This skill assumes `audit-code` has already passed. Don't waste a reviewer's attention on hygiene issues you could have caught yourself. ## Process ### 1. Prepare the review brief Write a self-contained brief for the reviewer agent. Include: - What was built (feature description, not implementation) - Which files changed (the diff context) - What `specs/` artifacts are relevant (active `epics/eNN-*.yaml`, `requirements/SCOPE_LATEST.yaml`, `bugs/BUG-*.md`) - What CONVENTIONS.md requires - What the verify command is - What you're most uncertain about (where you want fresh eyes) ### 2. Dispatch the reviewer agent Use the Agent tool with a completely fresh context. The agent prompt must be self-contained — no references to "our conversation" or "what we discussed." ``` You are a code reviewer. Review the following code changes. Context: [feature description] CONVENTIONS.md rules: [paste relevant sections] Active epic shard: [paste or summarize from specs/epics/] Diff: