product-thinking

Generates a structured Product Thinking Brief through five guided product strategy exercises.

11|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/qa-aman/next-leap-claude-code --skill product-thinking-qa-aman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-thinking
Source: https://github.com/qa-aman/next-leap-claude-code/tree/main/.claude/skills/product-thinking
Command: npx skills add https://github.com/qa-aman/next-leap-claude-code --skill product-thinking-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product managers often jump straight into writing PRDs without structured thinking, resulting in specs built on assumptions rather than evidence. This Skill runs five structured exercises before any spec writing, producing a Product Thinking Brief grounded in personas, feedback, and competitive context. ## Core Features & Use Cases - Problem Statement Builder: Defines who has the problem, supporting evidence, cost of inaction, and why it remains unsolved. - 11-Star Experience Ladder: Maps star levels 1 through 11 for a specific feature using Brian Chesky's framework, then selects a realistic target level. - Positioning & Principles: Drafts a Geoffrey Moore positioning statement and 3-5 falsifiable product principles with violation examples. - Success Vision with Kill Criteria: Writes a 6-month outcome narrative including behavior change expectations and explicit kill criteria. - Use Case: Before writing a PRD for a Smart Follow-Up feature, run the five exercises to produce a validated brief that feeds directly into spec writing. ## Quick Start Run the product thinking exercises for my new feature idea and output a Product Thinking Brief.

Frequently Asked Questions about product-thinking

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

FAQPage Schema
How do I structure product thinking before writing a PRD?▼

Run five sequential exercises: define an evidence-based problem statement, map an 11-star experience ladder, write a Geoffrey Moore positioning statement, set 3-5 falsifiable product principles, and draft a success vision with kill criteria. The output is a Product Thinking Brief that feeds into spec writing.

What is the 11-star experience framework for product features?▼

The 11-star framework, from Brian Chesky, asks what a 1-star through 11-star experience looks like for a specific feature. You describe levels 1, 3, 5, 7, 9, and 11, then pick a realistic target, typically 5-7 stars for production features.

How do I write a positioning statement using Geoffrey Moore's framework?▼

Use the template: For [target users], who [need/pain], [product] is a [category] that [key benefit]. Unlike [competitors], it [differentiator]. Pull target users from persona files and include the current manual process as a competitor when no direct rival exists.

When should I run product thinking exercises versus writing a spec directly?▼

Run the exercises whenever you have a raw feature idea that lacks evidence, positioning, or success criteria. Skip them only when a validated brief already exists, since the brief is the required input for quality spec writing.

What are kill criteria in a product success vision?▼

Kill criteria are explicit evidence thresholds that would justify stopping a feature, such as adoption or retention floors. Defining them upfront prevents sunk-cost continuation and is a required section of the success vision exercise.