{"id":"021-problem-framing","name":"021-problem-framing","summary":"問題や問題がより深い分析を始める前に明確な枠組みが必要な場合に使用してください。例えば、問題声明、現状、望ましい状態、ステークホルダー、成功基準の確立です。","body":"# Problem Framing\n\nGuide 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**.\n\n**What is covered in this Skill?**\n\n- Stating the problem independently of any specific solution\n- Describing the current state using observable facts\n- Describing the desired state as an outcome, not an implementation mechanism\n- Identifying stakeholders affected by, accountable for, or informed about the problem\n- Defining success criteria that make problem resolution verifiable\n- Feeding a clarified problem frame into `022-root-cause-analysis` and the remaining Functional Specification lenses\n\n## Constraints\n\nFrame 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.\n\n- **MUST** read `references/021-problem-framing.md` before applying Problem Framing guidance\n- **MUST** state the problem independently of any specific solution, technology, or implementation\n- **MUST** describe the current state using observable facts, not opinions or assumed causes\n- **MUST** describe the desired state as an outcome or capability, not a specific mechanism\n- **MUST** identify stakeholders affected by, accountable for, or informed about the problem, not only the requester\n- **MUST** define success criteria that are observable or measurable\n- **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\n\n## When to use this skill\n\n- Frame this problem before deeper analysis\n- Apply problem framing to this issue\n- Establish the problem statement, current state, and desired state\n- Identify stakeholders and success criteria for this problem\n- Draft the Problem Framing section of a Functional Specification\n\n## Workflow\n\n1. **Read the Reference**\n\nRead `references/021-problem-framing.md`, then identify what evidence is already available for the problem statement, current state, desired state, stakeholders, and success criteria.\n\n2. **Separate the Problem from any Solution**\n\nStrip out wording that already assumes a fix, technology, or implementation, and restate the gap in observable terms.\n\n3. **Describe Current and Desired State**\n\nDescribe the current state as observable facts and the desired state as a target outcome or capability.\n\n4. **Identify Stakeholders and Success Criteria**\n\nList stakeholders affected by, accountable for, or informed about the problem, then define observable or measurable success criteria.\n\n5. **Report the Problem Frame**\n\nReport the Problem statement, Current state, Desired state, Stakeholders, and Success criteria, and flag any field left open pending a clarifying answer.\n\n## Reference\n\nFor detailed guidance, examples, and constraints, see [references/021-problem-framing.md](references/021-problem-framing.md).","author":"@jabrena","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/jabrena/plinth/tree/main/skills/021-problem-framing","license":"Apache-2.0","category":"design","lang":"en","tokens":593,"stars":0,"calls30d":2,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[{"path":"references/021-problem-framing.md","size":7133,"sha256":"be6c5f87984a6b924c95c06e3877f38ad443b650743ed9cdffd099eb075ee9be"}],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}