review

<!-- rig-generated --> # review+ — Compliance Review Wraps `superpowers:requesting-code-review`. Requires superpowers to be installed. ## Procedure ### Phase A: Gather Review Context 1. Load the plan from `docs/plans/`. 2. Get the list of files changed since the plan was created: ``` git diff --name-only [plan-commit]..HEAD ``` 3. Invoke the scout agent to get current codebase state for comparison: ``` Agent(subagent_type="scout", prompt="Get current state of these files: [changed files list]. For each file, report: symbol count, key exports, test coverage status.") ``` ### Phase B: Spec Compliance Review 1. Dispatch the typed spec reviewer with the per-task payload (role content lives in the agent definition): ``` Agent(subagent_type="spec-reviewer", prompt="Task requirements: [full task text from the plan]. Implementer's report: [what was claimed/committed for this task]. Verify the implementation matches the spec — nothing more, nothing less.") ``` If the typed agent is unavailable, fall back to a general-purpose subagent using the superpowers spec-reviewer prompt template. 2. The spec reviewer verifies, for each task in the plan: - Check: was the task implemented? (file exists, code present) - Check: does the implementation match the plan's specification? - Check: are the specified tests present and passing? - Check: were any plan tasks skipped or significantly changed? 3. Check stale test status: - For eac...