review-aslisted

# review-as ## Usage **When to use:** Before sharing a PRD, strategy doc, launch plan, or any product artefact with a specific stakeholder whose review style has been captured as a lens. Also for applying a reusable framework lens to a draft. **Inputs:** - **Lens name** (required) — one or more comma-separated names from `knowledge/perspectives/`. E.g. `jane-vp-product` or `jane-vp-product,marcus-head-design` - **Draft** — the PRD, strategy doc, exec preso, or other artefact to review **Output:** Per-lens scored verdicts (1–5 scale), per-lens top-3 fix lists, a synthesis block (agreements, contradictions, priority-ordered combined fix list), and — for stakeholder lenses — an attribution footer for closing the loop with the stakeholder. **Built-in lenses (start here):** Six role lenses ship with the repo — `cpo`, `cto`, `coo`, `board`, `designer`, `engineer`. Try `review-as cpo` on any strategy doc right now, no setup needed. **Adding stakeholder-specific lenses:** Lenses are captured directly from the stakeholders who will review your work — not written by you about them. Here's how: 1. Identify the stakeholder whose review you most want to simulate (your VP, a key investor, a lead engineer) 2. Share `templates/stakeholder-lens-elicitation.md` with them — it's a short structured conversation they run in claude.ai, no install needed, ~10 minutes 3. They paste the output back to you; you save it as `knowledge/perspectives/{their-name}.md` 4. Now `review-as {their-name}`