product-thinking

Structure ambiguous product questions into clarified goals and actionable decisions.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/aidenz0/product-manager --skill product-thinking-aidenz0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-thinking
Source: https://github.com/aidenz0/product-manager/tree/main
Command: npx skills add https://github.com/aidenz0/product-manager --skill product-thinking-aidenz0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps product managers and teams turn fuzzy, request-driven product questions into focused problems that can be validated and acted upon, reducing wasted effort on unproven features or reactive competitive copying.

Core Features & Use Cases

  • Structured Four‑step Workflow: Guides Clarify → Deconstruct → Simplify → Decide to reframe problems, identify facts and constraints, remove unnecessary complexity, and produce actionable decisions.
  • Templates & Reference Library: Provides output patterns, trigger questions, and domain references (MVP, metrics, discovery, anti-patterns) to standardize analysis and experiments.
  • Practical Use Cases: Feature evaluation (e.g., whether to build social sharing), MVP scoping for new products, complexity reduction of bloated products, and prioritization with measurable validation plans.

Quick Start

Analyze this product request and return a Clarify, Deconstruct, Simplify, and Decide plan with an MVP recommendation and concrete next steps.

Frequently Asked Questions about product-thinking

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

FAQPage Schema
How do I turn vague product requests into clear decisions and actionable plans?

To turn vague product requests into clear decisions, use a structured Clarify, Deconstruct, Simplify, and Decide workflow that reframes ambiguous problems, exposes hidden assumptions, and outputs concrete next steps for validation.

What is the best way to scope an MVP for a new product feature?

The best way to scope an MVP is to deconstruct the product request into facts and constraints, simplify solution options by removing unnecessary complexity, and prioritize experiments with measurable validation plans.

How do I map hidden assumptions and constraints when evaluating product features?

Mapping hidden assumptions requires prompt reframing to classify hard and soft constraints, expose unproven logic, and compare solution complexity before committing to feature development.

Can I use a decision framework to prioritize user feedback and roadmap decisions?

Yes, a product decision framework can analyze user feedback by clarifying goals, decomposing facts, simplifying options, and producing prioritized experiments to guide measurable roadmap decisions.

When should I use assumption mapping for product discovery instead of directly building requested features?

Use assumption mapping for product discovery when facing fuzzy, request-driven questions to reduce wasted effort on unproven features and avoid reactive competitive copying.

Does this product thinking approach work for reducing complexity in bloated products?

Yes, this approach works for reducing complexity in bloated products by simplifying solution options, removing unnecessary features, and focusing on measurable validation plans and core user value.