product-lens

Generate a structured product brief with risks and a go/no-go recommendation.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/GGEdu/claude-god-mode-template --skill product-lens-ggedu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-lens
Source: https://github.com/GGEdu/claude-god-mode-template/tree/main/skills/product-lens
Command: npx skills add https://github.com/GGEdu/claude-god-mode-template --skill product-lens-ggedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to articulate the core rationale for new features, leading to scope creep and misaligned outcomes.

Core Features & Use Cases

  • Mode 1: Product Diagnostic — asks the hard questions to surface a crisp product thesis.
  • Mode 2: Founder Review — evaluates project viability from founder's perspective across market, differentiation, and risks.
  • Mode 3: User Journey Audit — maps the current experience to identify friction and improvement opportunities.
  • Mode 4: Feature Prioritization — scores ideas to guide roadmap decisions under constraints.
  • Integration — can pair with browser QA and design-system audit tools to validate onboarding and usability.

Quick Start

Run Mode 1 on a new feature to generate a structured product brief including questions and recommended next steps.

Frequently Asked Questions about product-lens

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

FAQPage Schema
How do I validate product rationale before building a new feature?▼

To validate product rationale, you need structured inquiry to surface a crisp product thesis. Applying diagnostic questions to early-stage ideation generates a concise brief, risks, and a go/no-go recommendation.

What is the best way to prioritize product features under constraints?▼

Feature prioritization under constraints requires scoring ideas to guide roadmap decisions. Evaluating ideas against specific scoring criteria outputs a prioritized list that aligns with project limitations.

How do I map user journey friction for product diagnostics?▼

Mapping user journey friction involves auditing the current experience to identify improvement opportunities. This audit highlights specific pain points in the user flow, providing actionable areas for product refinement.

Can I evaluate project viability from a founder's perspective during product scoping?▼

Evaluating project viability from a founder's perspective assesses market potential, differentiation, and risks. This review process outputs an objective viability check to support early-stage product scoping decisions.

Does product diagnostic integration work with browser QA and design-system audit tools?▼

Product diagnostic integration pairs effectively with browser QA and design-system audit tools. This combination validates onboarding flows and usability, ensuring the feature scope aligns with actual user interactions.

When should I run a product diagnostic to prevent scope creep?▼

Run a product diagnostic during early-stage ideation and ongoing reviews to prevent scope creep. Enforcing structured inquiry before building ensures teams articulate a clear rationale, avoiding misaligned outcomes.