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
SkillScore91Maintained
Automatic
◆Product Management pack
Last verified 8/20/2026
What it changes
Passed 20 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill91%
Checks it passed that the model alone missed
Avoids making up target cycle time numbers.
Flags missing error rates as clarifying questions.
Refrains from inventing specific numerical error targets.
and 15 more in the full report
14 fixed6 passed either way2 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+10%
Agent turns
0%
Response time
-13%
Model gemini-3.6-flashMeasured 8/20/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
Our customer support team is reporting high drop-off rates on the mobile checkout page, and management wants us to migrate to React Native to fix it. Before jumping into technical fixes, can you help us structure this issue properly? Please organize the background information into a formal breakdown containing the core problem statement, the current state, the desired target outcome, key impacted stakeholders, and measurable success criteria.
What was checked, without and with the skill
Checked
Without skill
With skill
Framed problem statement excludes React Native technology references.
Missed
Passed
Current state relies on reported checkout drop-off rates without assuming underlying framework flaws.
Passed
Passed
Flags missing baseline metrics and target values as clarifying questions instead of inventing numbers.
Missed
Passed
case-01 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md58 lines2 files
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
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.