021-problem-framing
/021-problem-framing
Use 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
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use 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
Original author description
Use 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
How it works
- Constraints
- When to use this skill
- Workflow
- Reference
SKILL.md preview
--- name: 021-problem-framing description: Use 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 license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Problem Framing Guide production of a Problem statement, Current state, Desired state, Stakeholders, and Success criteria for a problem or issue under exploration. **This is an interactive SKILL**. **What is covered in this Skill?** - Stating the problem independently of any specific solution - Describing the current state using observable facts - Describing the desired state as an outcome, not an implementation mechanism - Identifying stakeholders affected by, accountable for, or informed about the problem - Defining success criteria that make problem resolution verifiable - Feeding a clarified problem frame into `022-root-cause-analysis` and the remaining Functional Specification lenses ## Constraints Frame the problem before any deeper analysis. When this technique is orchestrated by another workflow, the orchestrator owns clarifying-question sequencing; when applied standalone, ask directly. - **MUST** read `references/021-problem-framing.md` before applying Problem Framing guidance - **MUST** state the problem independently of any specific solution, technology, or implementation - **MUST** describe the current state using observable facts, not opinions or assumed causes - **MUST** describe the desired state as an outcome or capability, not a specific mechanism - **MUST** identify stakeholders affected by, accountable for, or informed about the problem, not only the requester - **MUST** define success criteria that are observable or measurable - **MUST NOT** invent a problem statement, state, stakeholder, or success criterion when the available content is vague or ambiguous; flag the gap for a clarifying question instead ## When to use this skill - Frame this problem before deeper analysis - Apply problem framing to this issue - Establish the problem statement, current state, and desired state - Identify stakeholders and success criteria for this problem - Draft the Problem Framing section of a Functional Specification ## Workflow 1. **Read the Reference** Read `references/021-problem-framing.md`, then identify what evidence is already available for the problem statement, current state, desired state, stakeholders, and success criteria. 2. **Separate the Problem from any Solution** Strip out wording that already assumes a fix, technology, or implementation, and restate the gap in observable terms. 3. **Describe Current and Desired State** Describe the current state as observable facts and the desired state as a target outcome or capability. 4. **Identify Stakeholders and Success Criteria** List stakeholders affected by, accountable for, or informed about the problem, then define observable or measurable success criteria. 5. **Report the Problem Frame** Report the Problem statement, Current state, Desired state, Stakeholders, and Success criteria, and flag any field left open pending a clarifying answer. ## Reference For detailed guidance, examples, and constraints, see [references/021-problem-framing.md](references/021-problem-framing.md).
Files in this package (2)
- SKILL.md 3 KB
- references/021-problem-framing.md 7 KB
Versions
The database has no other skills named 021-problem-framing.
Database snapshot: 13.11.2026 · package version 528b7c3f6526 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100023-assumption-analysis
Use when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan. This should trigger when an issue's Assumption Analysis point of view needs evaluation, or when a maintainer… - 100024-context-mapping
Use when a problem under exploration needs its surrounding system context identified before design begins — Existing systems, Integrations, Ownership, and External dependencies. This should trigger when an issue's Context Mapping point of view needs evaluation, or when a… - 100022-root-cause-analysis
Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view needs evaluation, or when… - 100problem-framing-canvas
Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions. - 90uxd-problem-brief-create
Frame a product problem as a brief: who is affected, the current condition, evidence versus assumptions, and what is in scope. Use when framing a problem, writing a problem statement, or preparing an experience narrative. - 100problem-framing
Produce a Problem Frame — the pre-research artifact that grounds an engagement in the people-problem (no solution nouns), the decisions the product must enable, the gap between what stakeholders want and what is feasible, a known/unknown data map, a named stakeholder alignment…