product-thinking

Frame pre-implementation tasks by validating user demand and minimizing feature scope.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common pitfall of building features that lack clear user demand or suffer from excessive, unvalidated scope.

Core Features & Use Cases

  • Demand Validation: Forces the identification of specific user needs rather than abstract requirements.
  • Scope Optimization: Guides the agent to define the smallest possible version of a feature that delivers real value.
  • Assumption Surfacing: Explicitly highlights unvalidated assumptions during the design and planning phases to prevent gold-plating.

Quick Start

Apply the product-thinking lens to the current task to ensure the proposed feature serves a specific user need and avoids unnecessary complexity.

Frequently Asked Questions about product-thinking

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

FAQPage Schema
How do I validate user demand before building a new feature?

To validate user demand, you must identify specific user needs and surface unvalidated assumptions during the design phase. This prevents building features based on abstract requirements by forcing evidence-based reasoning before implementation begins.

What is the best way to minimize feature scope during product development?

Minimizing feature scope requires defining the smallest possible version of a feature that delivers real value. By applying a cognitive lens to slice tasks, you avoid unnecessary complexity and gold-plating during implementation planning.

How do I surface hidden assumptions in product design and planning?

Surfacing hidden assumptions requires applying a reasoning framework to explicitly highlight unvalidated claims during the design phase. This cognitive lens forces agents to frame goals around evidence rather than assertion, preventing scope creep.

Can I integrate demand validation into my existing development lifecycle?

You can integrate demand validation into your development lifecycle by applying it within the QRSPI workflow. It operates as a pre-implementation lens to influence task framing, design decisions, and implementation planning.

Why does my product management strategy suffer from unvalidated scope?

Product management strategy suffers from unvalidated scope when features lack clear user demand and rely on assertion over evidence. Without explicitly surfacing assumptions during design, features accumulate unnecessary complexity and gold-plating.