Skip to main content
Kodelyth ECC
Skill

product-lens

Use this skill to validate the "why" before building, run product diagnostics, and pressure-test product direction before the request becomes an implementation contract.

Invoke via:use product-lens
Origin:ECC

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")

  • What's the pain? (quantify: how often, how bad, what do they do today?)
    • 

  • Why now? (what changed that makes this possible/necessary?)
    • 

  • What's the 10-star version? (if money/time were unlimited)
    • 

  • What's the MVP? (smallest thing that proves the thesis)
    • 

  • What's the anti-goal? (what are you explicitly NOT building?)
    • 

  • 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

  • Infer: what is this trying to be?
    • 

  • Score: product-market fit signals (0-10)
    • 

   - Usage growth trajectory
   - Retention indicators (repeat contributors, return users)
   - Revenue signals (pricing page, billing code, Stripe integration)
   - Competitive moat (what's hard to copy?)

  • Identify: the one thing that would 10x this
    • 

  • Flag: things you're building that don't matter
    •

Mode 3: User Journey Audit

Maps the actual user experience:

1. Clone/install the product as a new user

  • Document every friction point (confusing steps, errors, missing docs)
    • 

  • Time each step
    • 

  • Compare to competitor onboarding
    • 

  • Score: time-to-value (how long until the user gets their first win?)
    • 

  • Recommend: top 3 fixes for onboarding
    •

Mode 4: Feature Prioritization

When you have 10 ideas and need to pick 2:

1. List all candidate features

  • Score each on: impact (1-5) × confidence (1-5) ÷ effort (1-5)
    • 

  • Rank by ICE score
    • 

  • Apply constraints: runway, team size, dependencies
    • 

  • Output: prioritized roadmap with rationale
    •

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

← All skills