product-lenslisted

# Product Lens — Think Before You Build This lane owns product diagnosis, not implementation-ready specification writing. If the user needs a durable PRD-to-SRS or capability-contract artifact, hand off to `product-capability`. ## When to Use - Before starting any feature — validate the "why" - Weekly product review — are we building the right thing? - When stuck choosing between features - Before a launch — sanity check the user journey - When converting a vague idea into a product brief before engineering planning starts ## How It Works ### Mode 1: Product Diagnostic Like YC office hours but automated. Asks the hard questions: ``` 1. Who is this for? (specific person, not "developers") 2. What's the pain? (quantify: how often, how bad, what do they do today?) 3. Why now? (what changed that makes this possible/necessary?) 4. What's the 10-star version? (if money/time were unlimited) 5. What's the MVP? (smallest thing that proves the thesis) 6. What's the anti-goal? (what are you explicitly NOT building?) 7. How do you know it's working? (metric, not vibes) ``` Output: a `PRODUCT-BRIEF.md` with answers, risks, and a go/no-go recommendation. If the result is "yes, build this," the next lane is `product-capability`, not more founder-theater. ### Mode 2: Founder Review Reviews your current project through a founder lens: ``` 1. Read README, CLAUDE.md, package.json, recent commits 2. Infer: what is this trying to be? 3. Score: product-market fit signals (0-10) - U