spec-review-modeslisted

# Spec Review Modes Use this skill to review technical specs without collapsing into one vague style of feedback. ## Core rule Always choose **one primary mode** first. You may add a short secondary pass later, but do not blur all three into one undifferentiated review. The three modes are: - **Mode A — Quick Overview** - **Mode B — Strict Spec Audit** - **Mode C — Product / Architecture Lens** If the user does not choose, infer from intent: - Wants a fast scan / first impression / "先看有沒有大問題" → **Mode A** - Wants contradictions / ownership / API / type rigor → **Mode B** - Wants product depth / market sense / "這樣會不會太薄" → **Mode C** For detailed checklists and output scaffolds, read `references/review-checklists.md`. ## Before reading 1. Identify the root folder or top-level doc set. 2. Read directory structure first if the spec is multi-file. 3. Read `overview.md` and `schema-v0.md` first when present. 4. If there is a shared type file (`shared-types.md` or equivalent), read it before criticizing type drift. 5. Do not pretend to have read everything if you only sampled part of the stack. ## Mode A — Quick Overview Use this when the goal is speed and orientation. Focus on: - what the system is trying to do - whether the boundaries make sense - the most obvious strengths - the most dangerous ambiguities - what to read next Do: - summarize the stack in plain language - name the 2-5 biggest risks, not every nit - point out where the docs feel clean vs muddy - say wha