Agent skill · affaan-m
product-lens
Validate the why before building through four product diagnostics — a YC-style product diagnostic that produces PRODUCT-BRIEF.md with a go/no-go recommendation, a founder review scoring product-market-fit signals, a user journey audit measuring time-to-value, and ICE feature prioritization. Use when pressure-testing product direction, choosing between features, sanity-checking a launch, or converting a vague idea into a product brief.
What it needs
About 2k tokens when loaded.
What this skill does
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: 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: Mode 3: User Journey Audit Maps the actual user experience: Mode 4: Feature Prioritization When you have 10 ideas and need to pick 2: Output All modes output actionable docs, not essays. Every recommendation has a specific next step. Integration 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
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/product-lens--112681