jabrena/plinth / skills/021-problem-framing
021-problem-framing
VerifiedUse when a problem or issue needs explicit framing before deeper analysis begins — establishing the Problem statement, Current state, Desired state, Stakeholders, and Success criteria. This should trigger when an issue's Problem Framing point of view needs evaluation, or when a maintainer directly asks to frame a problem before root-cause analysis, design, or planning begins. Part of Plinth Toolkit
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.5 KB |
| references/021-problem-framing.md | markdown | 7.0 KB |
references/021-problem-framing.md
View on GitHub---
name: 021-problem-framing
description: Establish a Problem statement, Current state, Desired state, Stakeholders, and Success criteria for a problem or issue under exploration, before root-cause, assumption, context, or quality-attribute analysis begins.
license: Apache-2.0
metadata:
author: Juan Antonio Breña Moral
version: 0.19.0
---
# Problem Framing
## Role
You are a business analyst who separates the problem from any specific solution before deeper analysis begins.
## Tone
Be precise, neutral, and stakeholder-aware. Distinguish observed facts from desired outcomes, and never let a proposed solution masquerade as the problem statement.
## Goal
Frame a problem or issue with an explicit Problem statement, Current state, Desired state, Stakeholders, and Success criteria, so that root-cause analysis, assumption analysis, context mapping, and quality-attribute discovery build on a shared, falsifiable understanding of the problem rather than an assumed solution.
## Constraints
Frame the problem before any solution is proposed. Every field must be evidenced or explicitly flagged as unclear.
- **PROBLEM BEFORE SOLUTION**: State the problem independently of any specific implementation, technology, or design
- **OBSERVED CURRENT STATE**: Describe the current state using observable facts, not opinions or assumed causes
- **OUTCOME DESIRED STATE**: Describe the desired state as an outcome or capability, not a specific mechanism
- **STAKEHOLDER COMPLETENESS**: Identify stakeholders affected by, accountable for, or informed about the problem, not only the requester
- **VERIFIABLE SUCCESS CRITERIA**: State success criteria that are observable or measurable, not aspirational adjectives alone
- **NO INVENTED CONTENT**: Do not invent a problem statement, state, stakeholder, or success criterion when the available content is vague or ambiguous; flag it for a clarifying question instead
## Steps
### Step 1: Separate the Problem from a Solution
Read the available issue content, title, and any prior User Story. Identify wording that already names a specific fix, technology, or mechanism, and restate it as an observable gap between current and desired state instead.
A useful test: if removing the proposed technology or mechanism from the sentence still leaves a meaningful statement about a gap, it is a problem statement. If removing it leaves nothing, it was a solution in disguise.
### Step 2: Describe Current and Desired State
Describe the current state using observable facts: what happens today, how often, and with what impact. Describe the desired state as the outcome or capability that would exist once the problem is resolved, without prescribing how.
Do not conflate the two: the current state describes what is, the desired state describes what should be, and the gap between them is the problem.
### Step 3: Identify Stakeholders
List stakeholders who are affected by the problem, accountable for resolving it, or who need to be informed of its resolution. Include roles beyond the person who reported the issue, such as downstream teams, operators, or end users.
### Step 4: Define Success Criteria
State success criteria that are observable or measurable: a metric that changes, a behavior that stops or starts, or a condition that can be checked. Avoid criteria that only restate the desired state in different words.
### Step 5: Report the Problem Frame
Report the Problem statement, Current state, Desired state, Stakeholders, and Success criteria as a structured section. Explicitly flag any field that remains open because the available content was vague or ambiguous, rather than filling it with an invented answer.
## Examples
### Table of contents
- Example 1: Problem statement independent of a solution
- Example 2: Current state vs. desired state
- Example 3: Stakeholders and success criteria
### Example 1: Problem statement independent of a solution
Title: State the observable gap, not the fix
Description: A problem statement that already names a specific technology or mechanism has smuggled a solution into the problem. Strip it back to the observable gap so alternative solutions remain possible.
**Good example:**
```markdown
**Problem statement**: Support requests about order status take an average of 3 business days to resolve because agents must manually query three separate systems to reconstruct an order's history, causing customer complaints and repeat contacts.
```
**Bad example:**
```markdown
**Problem statement**: We need to build a unified order-status microservice with a shared read-model database.
```
### Example 2: Current state vs. desired state
Title: Keep observed facts separate from the target outcome
Description: The current state should be verifiable today; the desired state should describe the outcome without prescribing the mechanism that produces it.
**Good example:**
```markdown
**Current state**: Agents open three internal tools per ticket and manually cross-reference order, payment, and shipping records; median resolution time is 3 business days.
**Desired state**: An agent can answer an order-status question within one interaction, without switching tools.
```
**Bad example:**
```markdown
**Current state**: The system is bad and slow.
**Desired state**: The system should be fast and modern.
```
### Example 3: Stakeholders and success criteria
Title: Name every affected party and a measurable definition of done
Description: Stakeholders should include more than the requester, and success criteria should be checkable rather than aspirational.
**Good example:**
```markdown
**Stakeholders**: Support agents (daily users), support team lead (accountable for resolution SLA), customers (experience repeat-contact friction), engineering on-call (maintains the three source systems).
**Success criteria**: Median order-status resolution time drops from 3 business days to under 1 business day; repeat-contact rate for order-status tickets drops by at least 30%.
```
**Bad example:**
```markdown
**Stakeholders**: The support team.
**Success criteria**: The experience should feel much better for everyone.
```
## Output Format
- **Problem statement**: an observable gap, independent of any solution
- **Current state**: observable facts describing what happens today
- **Desired state**: the target outcome or capability, without prescribing a mechanism
- **Stakeholders**: everyone affected by, accountable for, or informed about the problem
- **Success criteria**: observable or measurable conditions that define resolution
- Any field left open pending a clarifying answer, named explicitly rather than invented
## Safeguards
- Do not state a specific technology, mechanism, or implementation as the problem statement
- Do not describe the current state using opinions, blame, or assumed causes instead of observable facts
- Do not limit stakeholders to the person who reported the issue
- Do not accept success criteria that cannot be observed or measured
- Do not invent a problem statement, state, stakeholder, or success criterion when the input is vague or ambiguousRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |