メニュー
Frame problems using JTBD Job Stories, HMW questions, and persona validation
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | problem-framing |
| description | Frame problems using JTBD Job Stories, HMW questions, and persona validation |
Frame problems effectively using Jobs-to-be-Done, How Might We questions, and persona validation from Notion.
Create a Job Story in this format:
When [situation/context],
I want to [motivation/action],
So I can [expected outcome/benefit].
Example:
When I'm managing multiple client workspaces,
I want to switch between them quickly,
So I can respond to urgent requests without losing context.
Reframe the problem as an opportunity question:
How might we [opportunity that addresses the job story]?
Guidelines:
Example:
How might we help users navigate between workspaces seamlessly?
Fetch relevant personas from Notion database:
Search for personas database:
API-post-search with query "Personas" or "User Personas"
Query the database:
API-query-data-source with database_id from search results
Get persona details:
API-retrieve-a-page + API-get-block-children for each relevant persona
Extract these fields:
Validate the problem addresses all three job dimensions:
| Dimension | Question | Example |
|---|---|---|
| Functional | What task are they completing? | "Switch between workspaces" |
| Emotional | How do they want to feel? | "In control, not overwhelmed" |
| Social | How do they want to be perceived? | "Responsive, professional" |
After running this skill, output:
## Problem Framing
### Job Story
When [situation],
I want to [motivation],
So I can [outcome].
### How Might We
How might we [opportunity]?
### Relevant Personas
| Persona | Role | Goals | Pain Points |
|---------|------|-------|-------------|
| [Name] | [Role] | [Goals] | [Pain Points] |
### Three Dimensions
| Dimension | Definition |
|-----------|------------|
| Functional | [Task] |
| Emotional | [Feeling] |
| Social | [Perception] |
Invoke manually with "use problem-framing skill" or follow Ask mode DIVERGE loop which references this skill's phases.
design-context - Run after problem-framingcompetitor-scan - Research how others solve this problemConnect and verify the Well MCP — authenticate, confirm the tools work, and show what to ask. Use when the user runs /well:connect, just installed the Well plugin, or says the Well connection/MCP "isn't working" / "nothing happened".
Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace. Use when the user asks who owes them money, an AR aging report, overdue invoices, days sales outstanding (DSO), or which customers to chase.
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions. Use when the user asks for a cash-flow forecast, runway, how long until they run out of cash, projected balance, or expected inflows/outflows.
Run a month-end (or period) close checklist against a Well workspace — verify everything is reconciled and posted before the books are closed. Use when the user asks to close the month/period, run a close checklist, check if the books are ready to close, or what's left before closing.
Produce a VAT / sales-tax summary for a period from a Well workspace's posted ledger. Use when the user asks for a VAT return, VAT summary, sales tax owed, output vs input VAT, or tax declaration figures for a period.
Build a balance sheet (bilan) from a Well workspace. Use when the user asks for a balance sheet, bilan, assets/liabilities/equity, or financial position at a point in time.