problem-framing-canvas
Guide teams through MITRE's Problem Framing Canvas
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill problem-framing-canvasInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Tags
Our assessment of problem-framing-canvas
problem-framing-canvas scores 88/100 on our quality scale, 112th of 260 Design skills we index (top 44%).
Its SKILL.md is 18 KB long, well organised into 50 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so problem-framing-canvas is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
problem-framing-canvas compared with similar skills
All 4 of these similar skills score higher than problem-framing-canvas; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| problem-framing-canvas (this skill)by deanpeters | 88 | 7.1k | 3mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install problem-framing-canvas?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill problem-framing-canvas. The install tabs above show the steps for each supported agent. - Which AI agents does problem-framing-canvas work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is problem-framing-canvas safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is problem-framing-canvas still maintained?
- The repository was last updated about 3 months ago, so problem-framing-canvas is actively maintained.
Skill content
View source on GitHubname: problem-framing-canvas argument-hint: "[problem area]" description: Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions. intent: >- Guide product managers through the MITRE Problem Framing Canvas process by asking structured questions across three phases: Look Inward (examine your own assumptions and biases), Look Outward (understand who experiences the problem and who doesn't), and Reframe (synthesize insights into an actionable problem statement and "How Might We" question). Use this to ensure you're solving the right problem before jumping to solutions—avoiding confirmation bias, overlooked stakeholders, and solution-first thinking. type: interactive best_for:
- "Clarifying a messy problem before solutioning"
- "Surfacing assumptions and overlooked stakeholders"
- "Creating a bias-resistant problem statement in a workshop" scenarios:
- "Run a Problem Framing Canvas for our mobile retention issue"
- "Help me reframe this stakeholder request before we build anything"
- "We need a clearer problem statement for onboarding drop-off" theme: discovery-research estimated_time: "30-45 min"
Purpose
Guide product managers through the MITRE Problem Framing Canvas process by asking structured questions across three phases: Look Inward (examine your own assumptions and biases), Look Outward (understand who experiences the problem and who doesn't), and Reframe (synthesize insights into an actionable problem statement and "How Might We" question). Use this to ensure you're solving the right problem before jumping to solutions—avoiding confirmation bias, overlooked stakeholders, and solution-first thinking.
This is not a solution brainstorm—it's a problem framing tool that broadens perspective, challenges assumptions, and produces a clear, equity-driven problem statement.
Input
Works best with: The problem area — however roughly you currently understand it. Also useful: Who you believe experiences it, evidence so far, and the solution everyone is already anchored on (naming it helps the canvas de-bias it).
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The skill opens with the Look Inward phase: what do you assume about this problem?
Example invocation: Frame this problem: field sales reps 'don't use the CRM' and leadership wants gamification.
Key Concepts
What is the MITRE Problem Framing Canvas?
The Problem Framing Canvas (MITRE Innovation Toolkit, v3) is a structured framework that helps teams explore a problem space comprehensively before proposing solutions. It's partitioned into three areas:
- Look Inward — Examine your own assumptions, biases, and how you might be part of the problem
- Look Outward — Understand who experiences the problem, who benefits from it, and who's been left out
- Reframe — Synthesize insights into a clear, actionable problem statement and "How Might We" question
Canvas Structure
┌─────────────────────────────────────────────────────────────────┐
│ LOOK INWARD │
│ - What is the problem? (symptoms) │
│ - Why haven't we solved it? (new, hard, low priority, etc.) │
│ - How are we part of the problem? (assumptions, biases) │
└─────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────┐
│ LOOK OUTWARD │
│ - Who experiences the problem? When/where/consequences? │
│ - Who else has it? Who doesn't have it? │
│ - Who's been left out? │
│ - Who benefits when problem exists/doesn't exist? │
└─────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────┐
│ REFRAME │
│ - Stated another way, the problem is: [restatement] │
│ - How might we [action] as we aim to [objective]? │
└─────────────────────────────────────────────────────────────────┘
Why This Works
- Broadens perspective: Forces you to look beyond your own assumptions
- Equity-driven: Centers marginalized voices and asks "who's been left out?"
- Challenges biases: Requires explicit examination of assumptions before framing problem
- Actionable output: Produces HMW statement ready for solution exploration
Anti-Patterns (What This Is NOT)
- Not a solution brainstorm: Canvas frames the problem; solutions come later
- Not a feature request list: Focuses on underlying problems, not surface symptoms
- Not a one-person exercise: Requires diverse perspectives to challenge groupthink
When to Use This
- Starting discovery for a new initiative
- Reframing an existing problem (suspect you're solving the wrong thing)
- Challenging assumptions before building solutions
- Aligning cross-functional teams on problem definition
When NOT to Use This
- When the problem is already well-understood and validated
- For tactical bug fixes or technical debt (no deep framing needed)
- When stakeholders have already committed to a solution (address alignment first)
Facilitation Source of Truth
Use workshop-facilitation as the default interaction protocol for this skill.
It defines:
- session heads-up + entry mode (Guided, Context dump, Best guess)
- one-question turns with plain-language prompts
- progress labels (for example, Context Qx/8 and Scoring Qx/5)
- interruption handling and pause/resume behavior
- numbered recommendations at decision points
- quick-select numbered response options for regular questions (include
Other (specify)when useful)
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
Application
Use template.md for the full fill-in structure.
This interactive skill follows a three-phase process, asking adaptive questions in each phase.
Step 0: Gather Context (Before Questions)
Agent suggests:
Before we frame your problem, let's gather context:
Problem Context:
- Initial problem statement or stakeholder request
- Symptoms you've observed (support tickets, churn data, user complaints)
- Existing research (user interviews, surveys, analytics)
- Assumptions you're making about the problem
Stakeholder Context:
- Who's affected by this problem? (users, customers, internal teams)
- Who's asking for this to be solved? (execs, sales, customers)
- Who might have been overlooked?
You can paste this content directly, or describe the problem briefly.
Phase 1: Look Inward
Goal: Examine your own assumptions, biases, and how you might be part of the problem.
Question 1: What is the problem? (Describe symptoms)
Agent asks: "What is the problem as you currently understand it? Describe the symptoms."
Offer 4 enumerated options:
- Customer pain point — "Customers struggle with [specific task/outcome]" (e.g., "Customers can't find features they need")
- Business metric problem — "We're seeing [metric decline]" (e.g., "Churn increased 15% last quarter")
- Stakeholder request — "Stakeholders say we need [feature/change]" (e.g., "Sales team says we need better reporting")
- Observed behavior — "We've noticed [pattern/trend]" (e.g., "Users abandon onboarding at step 3")
Or describe your problem/symptoms.
User response: [Selection or custom]
Agent extracts:
- Problem (initial framing): [Description from user]
Question 2: Why haven't we solved it?
Agent asks: "Why hasn't this problem been solved yet?"
Offer 6 enumerated options (can select multiple):
- It's new — "Problem recently emerged"
- It's hard — "Technically complex or resource-intensive"
- It's low priority — "Other initiatives took precedence"
- Lack of resources — "Not enough budget, people, or time"
- Lack of authority — "Can't make the decision or get buy-in"
- A systemic inequity — "Problem disproportionately affects marginalized groups, overlooked"
Or describe your own reason.
User response: [Selection or custom]
Agent captures:
- Barriers to solving: [List of reasons]
Question 3: How are we part of the problem? (Assumptions & biases)
Agent asks: "How might you (or your team) be part of the problem? What assumptions or biases are you bringing?"
Offer 4 enumerated options:
- Assuming we know what customers want — "We haven't validated with real users" (Confirmation bias)
- Optimizing for ourselves, not users — "Building what's easy for us, not what's valuable for them" (Internal bias)
- Overlooking specific user segments — "Focused on majority users, ignored edge cases or marginalized groups" (Survivorship bias)
- Solution-first thinking — "Jumped to 'we need [feature X]' before understanding root problem" (Premature convergence)
Or describe your specific assumptions/biases.
User response: [Selection or custom]
Agent captures:
- Assumptions to challenge: [List of biases]
Phase 2: Look Outward
Goal: Understand who experiences the problem, who benefits from it, and who's been left out.
Question 4: Who experiences the problem? (When, where, consequences)
Agent asks: "Who experiences this problem? When and where do they experience it? What consequences do they face?"
Agent prompts user to describe:
- Who: Specific personas, user segments, or roles
- When: Triggering events or contexts (e.g., "during onboarding," "at month-end close")
- Where: Physical or digital locations (e.g., "mobile app," "enterprise deployments")
- Consequences: Impact on users (e.g., "waste 2 hours/week," "miss deadlines," "churn")
Adaptation: Use personas from context (proto-personas, JTBD, customer research)
User response: [Detailed description]
Agent captures:
- Who experiences it: [Personas/segments]
- When/where: [Context]
- Consequences: [Impact]
Question 5: Who else has this problem? Who doesn't have it?
Agent asks: "Who else has this problem? (Colleagues, competitors, other domains?) And who doesn't have it?"
Agent prompts:
- Who else has it: Other companies, industries, or domains with similar problems
- How do they deal with it: Workarounds, solutions, or adaptations
- Who doesn't have it: Users/companies that avoid the problem (what's different about them?)
User response: [Detailed description]
Agent captures:
- Who else has it: [Examples]
- Who doesn't have it: [Counter-examples]
Question 6: Who's been left out? Who benefits?
Agent asks: "Who's been left out of the conversation so far? And who benefits when this problem exists or doesn't exist?"
Agent prompts:
- Who's been left out: Marginalized voices, edge cases, overlooked stakeholders
- Who benefits when problem exists: Who gains from the status quo?
- Who benefits when problem doesn't exist: Who loses if problem is solved?
Example:
- "Who benefits when onboarding is broken?" → "Sales team doesn't have to support complex workflows; engineering doesn't have to build guided flows"
- "Who's been left out?" → "Non-technical users, international customers (onboarding in English only)"
User response: [Detailed description]
Agent captures:
- Who's been left out: [List]
- Who benefits (problem exists): [List]
- Who benefits (problem solved): [List]
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
