bs-problem

Create JTBD statements, testable hypotheses, and success metrics from brainstorm documents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-problem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bs-problem
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/brainstorming/skills/bs-problem
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-problem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts vague brainstorm ideas into a measurable problem definition by producing JTBD statements, prioritized testable hypotheses, and concrete success metrics that guide MVP scoping and validation planning.

Core Features & Use Cases

  • Focused discovery: Asks 6-8 targeted questions to clarify persona, context, current workarounds, constraints, and desired outcomes.
  • Structured outputs: Generates JTBD formatted statements, a hierarchy of hypotheses (H1 critical, H2 important, H3 nice-to-have) with metrics, thresholds, and experiment designs.
  • Deliverable file: Writes a comprehensive 800-1200 word brainstorm/02-problem-framing.md and updates the changelog for handoff to research or scoping.
  • Use case: Early-stage product teams converting a selected brainstorm concept into validation-ready hypotheses and metrics to prioritize MVP features and experiments.

Quick Start

Analyze brainstorm/01-brainstorm.md and brainstorm/00-assessment.md if present, ask six focused questions about users and constraints, then produce a JTBD statement, three prioritized testable hypotheses with metrics and experiments, and draft brainstorm/02-problem-framing.md.

Frequently Asked Questions about bs-problem

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

FAQPage Schema
How do I convert brainstorm ideas into testable hypotheses with success metrics?

JTBD statements are structured descriptions defining the job a user hires a product to do, specifying persona, context, and desired outcomes to translate vague ideas into measurable problem definitions for validation planning.

What is the best way to frame user problems for MVP validation?

The best way to frame user problems for MVP validation is to conduct focused discovery, ask targeted questions about constraints and workarounds, then produce JTBD statements and a hierarchy of prioritized hypotheses with experiment designs and success metrics.

Do I need an existing brainstorm document to start problem framing?

Yes, problem framing requires reading a brainstorm concept document and an assessment file when present, as these inputs provide the selected idea needed to generate validation-ready artifacts like JTBD statements and hypothesis hierarchies.

Can I use problem framing to define user personas and job stories for early-stage products?

Yes, you can use problem framing for early-stage products to define user personas and generate JTBD statements, which translate selected brainstorm concepts into structured job stories with measurable outcomes and validation-ready experiment designs.

How many hypotheses should a problem framing document include?

A problem framing document should include a hierarchy of three prioritized hypotheses: H1 as critical, H2 as important, and H3 as nice-to-have, each paired with measurable metrics, thresholds, and suggested experiments for validation.