product-think

Clarify fuzzy product requests into structured briefs with goals and risks.

163|43|Updated May 3, 2026
One-click install
npx skills add https://github.com/stella/stella --skill product-think
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-think
Source: https://github.com/stella/stella/tree/main/.agents/skills/product-think
Command: npx skills add https://github.com/stella/stella --skill product-think

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to define and align on the problem, user needs, and success criteria before starting implementation, reducing ambiguity.

Core Features & Use Cases

  • Problem framing: Clarify the user and the core need.
  • Option exploration: Compare multiple approaches and their trade-offs.
  • Product brief: Produce a concise brief detailing problem, users, goals, options, and risks.

Quick Start

Draft a concise product brief that defines the problem, user, goal, options considered, recommendation, risks, and success signals.

Frequently Asked Questions about product-think

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

FAQPage Schema
How do I turn a fuzzy product request into a structured product brief?

To create a structured product brief from a fuzzy request, clarify the core problem, identify user needs, explore trade-offs, and define measurable success signals. This ensures stakeholder alignment on goals and risks before development begins.

What is product thinking in the context of feature definition and roadmapping?

Product thinking is the process of framing a user need and clarifying the core problem before defining features. It involves exploring options and measuring success signals to ensure roadmapping decisions solve the right problem.

How do I align stakeholders on product goals and trade-off explorations?

Align stakeholders on product goals by producing a concise brief that details the problem, users, goals, options considered, and risks. Comparing multiple approaches during discovery ensures shared understanding of trade-offs.

Can I use problem clarification for feature ideas during the discovery phase?

Yes, problem clarification is applicable during discovery and ideation across feature ideas. It guides teams to define user needs and success criteria early, reducing ambiguity before starting implementation.

What is the best way to compare multiple approaches and their trade-offs during ideation?

The best way to compare approaches is to explore multiple options within a structured product brief. Documenting the problem, goals, and risks side-by-side ensures clear trade-off exploration and confident recommendations.

When should I not use a structured product brief for requirements gathering?

A structured product brief is unnecessary for straightforward requirements with zero ambiguity. If the problem, users, and success criteria are already clearly defined and stakeholder alignment is achieved, skip problem clarification.