problem-framing

Solid

Use when the user describes a goal but the underlying problem is unclear, or when a request feels like a premature solution.

AI & Automation 328 stars 19 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Problem Framing Translate a fuzzy request into a clear problem statement before any work begins. ## When to use - The user describes what they want but not why. - The request jumps to a specific solution. - Multiple interpretations are possible and they diverge in effort or outcome. ## Steps 1. Restate the request in plain language. Confirm with the user. 2. Ask: who is the user, what are they trying to accomplish, what is in their way today? 3. Identify hidden assumptions in the request and name them. 4. Offer 2-3 framings of the problem if more than one fits. Let the user pick. 5. State the chosen framing back as a single sentence the user can confirm. ## Anti-patterns - Restating jargon back without unpacking it. - Asking five clarifying questions at once. - Skipping confirmation and proceeding on a guess.

Details

Author: getcrew44
Repository: getcrew44/crew44
Created: 4 weeks ago
Last Updated: yesterday
Language: Go
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

problem-framing

Use when a team is converging on solutions before agreeing on the problem, when a brief reads as a feature request, when symptoms and root needs are tangled, or when assumptions need surfacing before design work proceeds. Do NOT use for code-level bug triage, runtime failure diagnosis, or root-cause analysis of system errors — those are engineering investigation tasks, not design problem framing.

0 Updated 1 weeks ago

jacob-balslev

Code & Development Listed

problem-framing

Turn an unclear request into a concrete engineering problem statement before implementation. Use when the user jumps to code, proposes a solution without the underlying problem, or asks for a fix without reproduction. NOT for pure formatting, copy edits, or already-scoped mechanical changes.

0 Updated 2 days ago

alinafe82

AI & Automation Listed

problem-framing

Use when decomposing a vague problem into a structured problem statement, identifying who has the problem and why it matters, sizing the opportunity, mapping constraints, prioritizing across multiple problems, or producing a Problem Definition Document that feeds into Discovery, Competitive Analysis, or Spec Writing. Encodes Problem Definition Canvas, 5 Whys Root Cause, JTBD Problem Framing, Opportunity Sizing, Problem-Solution Fit Assessment, Constraint Mapping, Stakeholder Impact Matrix, and ICE/RICE Prioritization.

4 Updated 2 weeks ago

Avyayalaya