product-lens

Use it when:: You're about to start a feature, are stuck choosing between ideas, or want a sanity check before a launch.
It does:: Asks who it's for, the pain, why now, the MVP and the anti-goal; or scores your repo's product-market-fit signals; or times onboarding as a new user.
You get:: A PRODUCT-BRIEF.md with risks and a go/no-go call, a scored founder review, three onboarding fixes, or a ranked roadmap.
Comes before:: ECC's product-capability, which turns a "build it" brief into an implementation plan.

TL;DR

ECC's product skill decides whether something is worth building, and leaves the spec to product-capability. It has four modes. The diagnostic works like automated YC office hours: seven questions on who the user is, how often and how badly the pain hits, why now, the 10-star version, the MVP, what you're explicitly not building and the metric that shows it works, ending in a PRODUCT-BRIEF.md with risks and a go/no-go recommendation. The founder review reads your README, CLAUDE.md, package.json and recent commits, infers what the project is trying to be, scores product-market-fit signals from 0 to 10, and names the one thing that would 10x it and what you're building that doesn't matter. The journey audit installs the product as a new user, logs and times every friction point, compares with competitors' onboarding and recommends three fixes. Feature prioritization scores ideas by impact times confidence divided by effort and returns a ranked roadmap with rationale.

Summarizes the skill at d2ef268.

npx skills add https://github.com/affaan-m/ecc --skill product-lens

skills.sh page Source on GitHub All skills from affaan-m/ecc

Total Downloads: 5,400 on skills.sh, Nov 9, 2026
Repo stars: 299,776 affaan-m/ecc
First seen: May 19, 2026 on skills.sh

Weekly Downloads

445

+74% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	256
Sep 28	164
Oct 5	144
Oct 12	238
Oct 19	419
Oct 26	410
Nov 2	480
Nov 9	445

Category	category:planning category:software-engineering Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:workflow A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect	effect:local Its own steps create or change files, git state or local tools.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:community Everyone else. Unverified vendor claims default to community.
Topics	requirements planning interview

SKILL.md

From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: product-lens
description: 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.
metadata:
  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")
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)
   - Usage growth trajectory
   - Retention indicators (repeat contributors, return users)
   - Revenue signals (pricing page, billing code, Stripe integration)
   - Competitive moat (what's hard to copy?)
4. Identify: the one thing that would 10x this
5. 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
2. Document every friction point (confusing steps, errors, missing docs)
3. Time each step
4. Compare to competitor onboarding
5. Score: time-to-value (how long until the user gets their first win?)
6. 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
2. Score each on: impact (1-5) × confidence (1-5) ÷ effort (1-5)
3. Rank by ICE score
4. Apply constraints: runway, team size, dependencies
5. 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