Skip to main content
affpapa.org
RU EN
skill Claude Code CX Codex Cursor GitHub Copilot

product-lens — Claude skill: product diagnostics before you build

The skill runs an idea or an existing project through four product diagnostics and returns a document with a go/no-go call. Useful when you cannot tell whether the thing is worth building.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add affaan-m/ECC --skill product-lens -a claude-code
Open on GitHub

What product-lens does

product-lens has four modes. The first is a YC-style product diagnostic: the skill asks hard questions about audience, pain, timing, the MVP and anti-goals, then writes PRODUCT-BRIEF.md with risks and a go/no-go recommendation. The second is a founder review: the agent reads README, CLAUDE.md, package.json and recent commits, infers what the project is trying to be, and scores product-market fit signals from 0 to 10.

Mode three audits the user journey. You install the product as a new user, log every friction point, time each step and measure time-to-value. Mode four prioritizes features by ICE: impact × confidence ÷ effort, then ranks them against constraints like runway and dependencies.

The skill does not write implementation-ready specs. When a brief needs to become a capability plan, it hands off to product-capability. Install it if you keep choosing between features and want the why checked before code. Skip it when product direction is settled and those questions no longer come up.

What it helps with

  • pressure-test an idea before writing code
  • pick two features out of ten with ICE scoring
  • score product-market fit from the repo and commit history
  • measure time-to-value during onboarding
  • turn a vague idea into PRODUCT-BRIEF.md

Example prompts for the agent

  • run product-lens on my idea and tell me if it's worth building
  • do a founder review of this project
  • audit the user journey and show me the top 3 onboarding problems

How to install product-lens

1Skills CLI (Vercel)

npx skills add affaan-m/ECC --skill product-lens -a claude-code

2Manually: put the files in place

~/.claude/skills/product-lens/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/product-lens/

From the same set146

The whole set →
video-editing affaan-m AI-assisted workflow for editing, trimming, and enriching real footage. Connects raw recordings with FFmpeg cuts, Remotion overlays, and ElevenLabs voiceovers. Claude Code CX Codex Cursor +1 6,500installs docker-patterns affaan-m A skill with Dockerfile and Docker Compose patterns: local dev stacks, networking, volumes, container hardening. Claude Code CX Codex Cursor +1 6,300installs frontend-patterns affaan-m A skill for React and Next.js work: component patterns, state, data fetching, and render performance. Use it when building or reviewing UI. Claude Code CX Codex Cursor +1 5,900installs backend-patterns affaan-m A skill with backend patterns for Node.js, Express and Next.js API routes: layering, caching, transactions, error handling. Claude Code CX Codex Cursor +1 5,900installs coding-standards affaan-m Baseline cross-project coding conventions for naming, immutability, and clean code principles. Useful for code reviews and refactoring. Claude Code CX Codex Cursor +1 5,600installs api-design affaan-m Provides REST API design standards covering resource naming, status codes, pagination, and error payloads. Use it when creating or auditing API contracts. Claude Code CX Codex Cursor +1 5,500installs rust-testing affaan-m A skill for writing Rust tests: unit, integration, async, property-based, mocks and coverage. Useful when the project runs on TDD. Claude Code CX Codex Cursor +1 5,500installs laravel-security affaan-m This skill reviews Laravel authentication, Eloquent safety, CSRF, XSS, APIs, and production settings. Use it for security reviews or deployment checks. Claude Code CX Codex Cursor +1 5,400installs

Similar

find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. Claude Code CX Codex Cursor +1 4,000,000installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. Claude Code 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. Claude Code 1,038,491installs grilling Matt Pocock Stress-test a plan, decision, or idea through structured rounds of questions. Use it when you need to expose assumptions before acting. Claude Code 979,543installs teach Matt Pocock Turns the current directory into a learning workspace and keeps progress across sessions. Use it when learning needs to support a concrete goal in your project. Claude Code 862,247installs

Questions about product-lens

How do I install product-lens in Claude?

Run npx skills add affaan-m/ECC --skill product-lens -a claude-code. The skill lands at ~/.claude/skills/product-lens/SKILL.md.

What does product-lens do?

It runs four diagnostics: a YC-style product diagnostic, a founder review scoring product-market fit, a user journey audit, and ICE feature prioritization. Each one outputs a doc with a specific next step.

What does the skill need to work?

The founder review needs access to README, CLAUDE.md, package.json and commit history. The user journey audit requires installing the product as a new user.

Source text

SKILL.md · MIT 
---
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

© affaan-m · MIT · affaan-m/ECC

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor