Product Lens
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of product-lens by affaan-m - installs and ranking accrue to the original listing.
product-lens is a Claude Code skill that pressure-tests product ideas and clarifies the why before coding for developers who receive vague feature requests and need scope validation before writing implementation code.
About
product-lens is an ECC-origin skill designed to challenge product assumptions and surface the underlying why before agents translate requests into code. Developers reach for product-lens when stakeholders hand over underspecified features, when the motivation behind a ticket is unclear, or when a quick sanity check could prevent building the wrong thing. The skill acts as a pre-build lens on intent, forcing clarity on user problems, success criteria, and tradeoffs instead of jumping straight to files and functions. It fits early validation workflows alongside prototyping and scoping skills. The published readme notes an in-progress Japanese translation, but the skill definition and description remain active in the ECC catalog for English-language product questioning sessions inside Claude Code agent workflows.
- 7-question Product Diagnostic checklist modeled after YC office hours
- Generates a PRODUCT-BRIEF.md with answers, risks, and go/no-go recommendation
- Explicitly separates product diagnosis from implementation specification
- Triggers handoff to product-capability skill when build decision is yes
- Prevents building the wrong thing by forcing quantification of pain, metrics, and anti-goals
Product Lens by the numbers
- 1,398 all-time installs (skills.sh)
- +83 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill product-lensAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you validate product ideas before coding?
Pressure-test product ideas and clarify the why before turning vague requests into code.
Who is it for?
Developers and tech leads receiving ambiguous feature asks who need structured product questioning before agent-driven coding.
Skip if: Teams with fully specified tickets and signed-off requirements who are ready to implement immediately.
When should I use this skill?
User presents a vague product idea, unclear feature request, or asks why before building something in code.
What you get
Clarified product rationale, scoped requirements, and documented assumptions before implementation starts.
Files
product-lens - 日本語翻訳進行中
このファイルの翻訳は実装中です。英語版は元のスキルファイルを参照してください。
詳細は：D:/tmp/everything-claude-code/skills/product-lens/SKILL.md
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What does product-lens do before coding?
product-lens pressure-tests product ideas and clarifies the why behind requests. The skill helps developers challenge assumptions and define scope so agents do not implement the wrong feature from vague input.
When should product-lens run in a workflow?
product-lens should run during validation before implementation when a feature request lacks clear motivation, success metrics, or scope. It precedes code generation skills in the ECC workflow.