product-lens

Interrogate user needs, pain points, and success criteria to produce product briefs and roadmaps.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/zardusai-cyber/zardus_setup --skill product-lens-zardusai-cyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-lens
Source: https://github.com/zardusai-cyber/zardus_setup/tree/main/ecc/skills/product-lens
Command: npx skills add https://github.com/zardusai-cyber/zardus_setup --skill product-lens-zardusai-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate the core rationale behind product ideas by surfacing user needs, pain points, and success criteria to ensure you're building the right thing.

Core Features & Use Cases

  • Product Diagnostic mode: asks hard questions about target users, pains, timing, and success metrics to produce a concise product brief.
  • Founder Review mode: evaluates README, CLAUDE.md, package.json, and recent commits to infer product intent and identify the single most impactful improvement.
  • User Journey Audit: maps the user experience to locate friction and quantifiably improve time-to-value.
  • Feature Prioritization: scores ideas on impact, confidence, and effort to output a prioritized roadmap.

Quick Start

Describe your idea, identify target users, and run the Product Lens to produce a concrete product brief and prioritized roadmap.

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 ideas and clarify user needs before development?

Validate product ideas by interrogating target users, pain points, and success criteria to produce a concise product brief. This ensures you build the right feature by surfacing the core rationale behind early-stage ideation before committing development resources.

What is the best way to prioritize features and build a product roadmap?

Prioritize features by scoring ideas on impact, confidence, and effort to output a prioritized roadmap. This quantifiable approach helps stakeholders make objective decision-making choices about which features to develop next based on clear success metrics.

How do I audit a user journey to locate friction and improve time-to-value?

Audit a user journey by mapping the user experience to locate friction points and quantifiably improve time-to-value. This process identifies specific bottlenecks in the user flow, allowing stakeholders to target areas that delay product value realization.

Can I evaluate existing product intent from codebase files like README and package.json?

Yes, you can evaluate product intent by analyzing README, CLAUDE.md, package.json, and recent commits. This Founder Review mode infers the product's direction and identifies the single most impactful improvement to prioritize in the roadmap.

When do I need to run a product diagnostic for feature vetting?

Run a product diagnostic during early-stage ideation, feature vetting, weekly reviews, and pre-launch sanity checks. It asks hard questions about target users, pains, and timing to ensure specification validation aligns with actual user needs before you build.

Do I need any specific dependencies or components to run product discovery workflows?

No dependencies or components are required to run product discovery workflows. You only need to describe your idea, identify target users, and run the diagnostic to produce a concrete product brief and prioritized roadmap document.