reviewlisted

# /bs:review - Collaborative Artifact Review **Usage**: `/bs:review <artifact-path[,artifact-path2]> [--type product|pdf|landing|email|doc|slides|general] [--goal sota|conversion|clarity|competitive] [--visual] [--persist <path>]` Use this when you want a serious collaborative review of a built artifact before shipping it: - product guides - PDFs - landing pages - email sequences - strategy docs - slide decks - general long-form written assets This is **not** a code-review command. For code, use `/bs:quality` or `/gh:review-pr`. ## Review Standard Default standard: **SOTA enough to ship confidently** That means the review should test for: - substance over padding - specificity over generic AI filler - strong buyer clarity - differentiated insight - structural completeness - conversion credibility where relevant - visual/layout quality when layout matters ## Step 1: Classify the Artifact Determine the artifact type from the flag or the file itself: - `product` — paid guide, playbook, starter kit, offer doc - `pdf` — exported artifact where layout matters - `landing` — sales or capture page copy - `email` — launch or nurture sequence - `doc` — general strategy or content draft - `slides` — deck or presentation - `general` — fallback when the shape is mixed Determine the review goal: - `sota` — overall quality and competitiveness - `conversion` — does this persuade and sell? - `clarity` — does this communicate cleanly? - `competitive` — does this feel differentiated