product-lens

Force explicit reasoning and surface hard truths before coding.

3|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/nassimbf/ftitos-claude-code --skill product-lens-nassimbf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-lens
Source: https://github.com/nassimbf/ftitos-claude-code/tree/main/skills/product-lens
Command: npx skills add https://github.com/nassimbf/ftitos-claude-code --skill product-lens-nassimbf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align product teams by forcing explicit reasoning before coding, surfacing hard truths, and preventing untested assumptions from driving decisions.

Core Features & Use Cases

  • Anti-sycophancy: Take a position, push on weak answers, and call out vagueness to demand clear reasoning.
  • Forcing Questions (Mode 1): Run through a structured question set to elicit concrete details before coding.
  • Founder Review (Mode 2): Evaluate the project thesis from a founder lens to infer alignment and PMF signals.
  • User Journey Audit (Mode 3): Map user flows and friction points to guide UX improvements.
  • Feature Prioritization (Mode 4): Score and rank features using a principled prioritization framework.
  • Output: Generates actionable docs and guardrails to guide the build process.

Quick Start

Run Mode 1 to force questions, then Mode 2–4 to validate and prioritize before building.

Frequently Asked Questions about product-lens

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a product idea before writing any code?

To validate a product idea before coding, you must force explicit reasoning and surface hard truths. Structured questioning evaluates user needs and project alignment, preventing untested assumptions from driving development decisions.

What is the best way to prioritize product features using a structured framework?

Prioritizing product features requires scoring and ranking them against a principled framework. This approach evaluates feature impact, aligns roadmap decisions with user needs, and generates guardrails to guide the build process.

How do you conduct a user journey audit to find UX friction points?

A user journey audit maps user flows to identify friction points and guide UX improvements. By evaluating how users interact with a concept, teams can pinpoint barriers and optimize the experience before development.

Can I use founder review modes to evaluate product-market fit signals?

Founder review modes evaluate the project thesis from a founder lens to infer alignment and product-market fit signals. This assessment pushes on weak answers, calls out vagueness, and demands clear reasoning.

Does anti-sycophancy reasoning help with product strategy and roadmapping?

Anti-sycophancy reasoning improves product strategy and roadmapping by taking a firm position and pushing on weak answers. It demands clear reasoning to prevent vague assumptions from driving feature prioritization.

When should I force explicit questions during early concept validation?

You should force explicit questions during early concept validation, weekly reviews, and major feature decisions. This structured approach surfaces hard truths, ensuring the build aligns directly with the user need.