reviewlisted

This skill is the **review** orchestrator. It runs three reviews — technical, security, then visual — against the code produced by `/build`, using `.design/YYYY-MM-DD-<slug>.md` as the yardstick. **Reviews print their findings and write no files.** Every finding carries a stable id so a fix pass can report against it; the record of what was fixed lands in the design file's `## Implementation` section, written by the fix pass, not here. This skill edits nothing. The three-part pipeline: - `/design` — produces `.design/YYYY-MM-DD-<slug>.md`. - `/build` — reads it, writes the code. - `/review` — this skill. Reviews the code against it. ## Prerequisites **Required:** code changes to review — uncommitted, a branch diff, or files the user names. If there's no diff and no target, ask which files to review. **Optional:** `.design/YYYY-MM-DD-<slug>.md`. It is the yardstick for *intent*, not a gate. Most branches don't have one, and a branch without a design still deserves a review. **No design file: ask, then do what they say.** Do not start a degraded review on your own judgment — the user may have meant a different slug, or may want `/design` first. State what you found and ask one question: > No design file for this branch. Review the diff on its own? Plan-gap and plan-drift checks get skipped — nothing to measure intent against. **They say yes** — run the review as described below. **They say no, or name a slug** — use it. Ask once; do not re-raise it at each phase. Once