problem-framer

Name: problem-framer
Availability: InStock
Author: thorstarlord

Structure vague ideas into a seven-section Problem Frame without proposing solutions.

1|Updated May 6, 2026

Search Tags:#documentation #root cause analysis #specification #requirements #product discovery #problem framing #sensemaking

Ready to run

npx skills add https://github.com/ThorStarlord/interface-skills --skill problem-framer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: problem-framer
Source: https://github.com/ThorStarlord/interface-skills/tree/main/skills/problem-framer
Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill problem-framer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps you replace an ambiguous idea or messy situation with a structured Problem Frame that clarifies the root tension, impacted boundary, and what success must look like.

Core Features & Use Cases

Problem Under the Problem analysis: identifies the deeper root cause, desire, or underlying tension behind the stated issue.
Object Under Pressure selection: pinpoints the specific system part that is most impacted or ambiguous so you focus your thinking.
Success and Failure alignment: defines the nightmare scenario and the conditions that would prove the solution is truly successful.
Use Case: when you have a “repository fog” situation where you know something is wrong or incomplete but cannot yet articulate what must be fixed or why.

Quick Start

Ask the AI to run the Problem Frame workflow for your situation and produce the full 7-section Problem Frame without proposing technical solutions.

Frequently Asked Questions about problem-framer

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

FAQPage Schema

How do I structure a vague product idea into clear requirements?▼

Problem framing transforms a vague product idea into clear requirements by identifying the root tension, pinpointing the object under pressure, and defining success conditions without proposing technical solutions.

What is the best way to perform root cause analysis on repository fog?▼

Performing root cause analysis on repository fog works best by structuring the ambiguous situation into a seven-section Problem Frame, clarifying the deeper underlying tension and impacted system boundaries before any specification is written.

How do I define product discovery boundaries for early sensemaking?▼

To define product discovery boundaries for early sensemaking, select the specific system part that is most impacted, then align the nightmare failure scenario with the conditions that prove true success.

Does problem framing output technical specifications or implementations?▼

No, problem framing does not output technical specifications or implementations; it explicitly forbids proposing specific solutions, focusing purely on structuring the problem space and boundary clarity.

When do I need to use a problem frame template instead of writing a specification?▼

You need to use a problem frame template instead of writing a specification during early sensemaking when you are unsure what you are building, utilizing a seven-section structure spanning from Raw Fog to Next Artifact to clarify the root cause.