skills.rest
mostafa-ismail-2004
mostafa-ismail-2004COMMUNITY
Explore all skills by this author →
GitHub

product-lens

Analyze product ideas against user need, severity, timing, and success criteria.

Updated Jun 24, 2026
Search Tags:#product validation#roadmap#user journey#product strategy#product brief#feature prioritization
One-click install
npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill product-lens-mostafa-ismail-2004
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-lens
Source: https://github.com/mostafa-ismail-2004/codex-plugin/tree/main/skills/product-lens
Command: npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill product-lens-mostafa-ismail-2004

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you validate whether a product idea is worth building before engineering effort starts, reducing wasted work on unclear or low-value features.

Core Features & Use Cases

  • Product diagnosis: Pressure-test the user, pain, timing, and success metrics behind a feature idea.
  • Founder review: Assess what a project is really trying to become by reading core project signals and identifying what would move it forward most.
  • User journey audit: Examine onboarding and workflow friction to find where users lose time or confidence.
  • Feature prioritization: Rank competing ideas by impact, confidence, and effort to produce a practical roadmap.
  • Use case: A team can use this Skill before planning a release to decide whether to build, refine, or drop a feature based on evidence.

Quick Start

Use the product-lens skill to evaluate this product idea and produce a concise product brief with risks, metrics, and a go or no-go recommendation.

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 engineering starts?▼

Validate a product idea by pressure-testing user need, problem severity, timing, and success metrics to produce an evidence-based product brief with a go or no-go recommendation.

What is the best way to prioritize features for a product roadmap?▼

Feature prioritization ranks competing ideas by impact, confidence, and effort to produce a practical roadmap. This approach ensures high-value features are built first based on evidence.

How do I audit user journey friction during onboarding?▼

Audit user journey friction by examining onboarding and workflow steps to find where users lose time or confidence, identifying specific pain points that reduce product adoption.

When do I need a product brief for feature decisions?▼

You need a product brief when deciding whether to build, refine, or drop a feature, ensuring teams avoid wasted work on unclear or low-value features before implementation begins.

Can I assess project direction and launch readiness without writing code?▼

Yes, you can assess project direction by reading core project signals to identify what moves it forward, checking launch readiness, and generating risk assessments without writing code.

Related Skills

Explore More Product & Management Skills→
ArvorCoArvorCo
96

prd

Generate a structured PRD with goals, user stories, and acceptance criteria.

Community
Basic
augustoheissaugustoheiss

agency-product-manager

Translate ambiguous business problems into validated product plans and PRDs.

Community
Advanced
LukasStricklerLukasStrickler
4

research

Synthesize academic and practical sources into evidence cards and research reports.

Community
Advanced
huuhiep0303huuhiep0303

idea-refine

Guide users through divergent and convergent thinking to refine raw ideas.

Community
Advanced