product-lens

Topics in the source

• Product Lens — Think Before You Build
• When to Use
• How It Works
• Mode 1: Product Diagnostic
• Mode 2: Founder Review
• Mode 3: User Journey Audit
• Mode 4: Feature Prioritization
• Output

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. 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 Like YC office hours but automated. Asks the hard questions: 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. Reviews your current project through a founder lens: Maps the actual user experience: When you have 10 ideas and need to pick 2: All modes output actionable docs, not essays. Every recommendation has a specific next step. Pair with: /browser-qa to verify the user journey audit findings /design-system audit for visual polish assessment /canary-watch for post-launch monitoring product-capability when the product brief needs to become an implementation-ready capability plan