Skip to main content
skill CX Codex

021-problem-framing — Claude Code skill: setup and usage

021-problem-framing structures problem statements, current and desired states, stakeholders, and success criteria before engineers jump into implementation.

Apache-2.0 139 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 021-problem-framing -a claude-code
Open on GitHub

What 021-problem-framing does

Part of the Plinth Toolkit, this interactive skill guides agents through framing an issue before root-cause analysis or design work begins. It forces the agent to isolate the core breakdown from proposed fixes or specific tools, keeping the focus strictly on observable evidence.

Execution follows a five-stage sequence. The agent first inspects references/021-problem-framing.md to gather facts. It then removes solution-biased language, documents the gap between current and desired states, catalogues affected parties, and records verifiable success metrics. Output feeds directly into subsequent lenses like 022-root-cause-analysis.

The skill strictly forbids guessing: whenever incoming descriptions lack clarity, the agent must flag the gap and ask questions rather than fabricating facts.

What it helps with

  • isolate problem statements from assumed technical fixes
  • document the current state using observable facts
  • define the desired outcome as a capability instead of a mechanism
  • identify parties affected by, accountable for, or informed about the issue
  • set verifiable success criteria for problem resolution

Example prompts for the agent

  • Frame this problem before we begin technical design
  • Apply problem framing to this issue and identify the current state
  • Draft the Problem Framing section with measurable success criteria

How to install 021-problem-framing

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 021-problem-framing -a claude-code

2Manually: put the files in place

~/.claude/skills/021-problem-framing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/021-problem-framing/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 021-problem-framing

How to install 021-problem-framing in Claude Code?

Run npx skills add jabrena/plinth --skill 021-problem-framing -a claude-code in your terminal. The prompt file installs to ~/.claude/skills/021-problem-framing/SKILL.md.

What does 021-problem-framing do?

It guides an interactive workflow to state a problem independently of solutions, list key stakeholders, and define clear success metrics.

What dependency does this skill check first?

It requires the agent to read references/021-problem-framing.md before applying framing rules or generating output.

Source text

SKILL.md · Apache-2.0
---
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).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set123

The whole set →
812-regulations-eu-product-liability-directive 812-regulations-eu-product-liability-directive turns EU Product Liability Directive 2024/2853 checks into engineering artefacts: scope inventory, hazardous-scenario tests, update history and user warnings for Java and AI products. CX Codex +1 165installs 810-regulations-eu-mifid-ii 810-regulations-eu-mifid-ii reviews Java enterprise applications for MiFID II investment service controls and audit evidence prior to release. CX Codex +1 165installs 022-root-cause-analysis 022-root-cause-analysis — a skill for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI that runs structured root cause analysis using Five Whys, Fishbone (Ishikawa), and Current Reality Tree. CX Codex +1 144installs 025-quality-attribute-discovery The 025-quality-attribute-discovery skill finds and ranks a solution’s quality attributes before architecture work begins. It ties each candidate to evidence from the problem and its context. CX Codex +1 143installs 024-context-mapping 024-context-mapping is a Claude Code skill that maps existing systems, integrations, owners, and external dependencies before design when system boundaries are undefined. CX Codex +1 142installs 023-assumption-analysis 023-assumption-analysis is a skill that identifies and ranks assumptions and unknowns in a framed problem before design, then outlines validation checks. CX Codex +1 140installs 059-design-atdd 059-design-atdd is a Claude Code skill that checks whether an OpenSpec change’s goal, acceptance criteria, and implementation or verification tasks agree. It produces an evidence-backed report of gaps and mismatches. CX Codex +1 135installs 058-design-bdd 058-design-bdd — a skill that takes Java teams through Behavior-Driven Development as collaborative discovery practice. Works with trusted behavior facts, concrete examples, and scenarios in shared domain language. CX Codex +1 135installs

Project sponsors

Companies that keep this analytics open