Product Lens

Use this before you write any code to validate whether you're solving the right problem. It runs product diagnostics by asking founder-style questions (who's this for, what's the pain, why now, what's the MVP), reviews your project through a PMF lens by analyzing your repo for growth signals, audits user journeys for friction points, and helps prioritize features with ICE scoring. Outputs actionable briefs, not essays. The honest take: this is the "stop building features nobody asked for" intervention. Pair it with product-capability when you've validated the why and need to translate it into an implementation plan. Most useful during weekly reviews or before kicking off any new feature work.

skills.sh installs: 3.9K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill product-lens --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub