メニュー
Design thinking methodology for human-centered problem solving. Use when facilitating design thinking workshops, user research sessions, or creative problem-solving activities.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Interactively elicit, capture, and maintain software/system requirements as a living, traceable repository. Use whenever the user wants to gather, write, refine, or organize requirements — including producing or updating an SRS (software/system requirements specification), writing ADRs / architecture decision records, building a requirements traceability graph (DAG), or keeping a decision ledger. Trigger proactively when the working folder already holds requirements artifacts (a `requirements/` folder of YAML, `decisions/` ADRs, an `srs.md`, or `ledger.md`), or when the user shares documents that are clearly specs, RFCs, or feature briefs and wants them structured. Also use for phrases like "let's spec this out", "interview me about what we're building", "capture these requirements", "write a decision record", or "turn these notes into a spec". Not for project management, code review, application code, dependency manifests like requirements.txt, or hardware "system requirements" (RAM/CPU).
Use this skill whenever the user wants to create a bash script that drives an autonomous coding loop — scripts that run Claude Code on a schedule (cron, GitHub Actions, systemd timer) or on-demand to make repository improvements, execute plans, triage issues, or otherwise do agentic work with minimal human intervention. Triggers include phrases like "scout script", "autonomous script", "agent harness", "script that runs on a schedule", "script that implements a plan", ".scripts/*.sh", or any request for a bash script whose body is "run Claude Code with a prompt and commit the results". Always use this skill before writing such a script — it encodes the interview flow, the adversarial-reviewer pattern, and the locking/ledger conventions.
Task structure and atomic commit patterns for granular, verifiable work units
Conflict identification and resolution patterns for requirements, decisions, and plans
Context window management techniques for maintaining efficiency and preventing context bloat
Exploration map management for tracking discussed areas and uncharted territory during DISCUSS phase
| name | design-thinking |
| description | Design thinking methodology for human-centered problem solving. Use when facilitating design thinking workshops, user research sessions, or creative problem-solving activities. |
| allowed-tools | Read, Grep, Glob, AskUserQuestion, Write |
Design Thinking is a human-centered approach to innovation and problem-solving. It integrates the needs of people, the possibilities of technology, and the requirements for business success.
Purpose: Understand the people you're designing for.
Key Activities:
Outputs:
Key Questions:
Purpose: Synthesize findings into a clear problem statement.
Key Activities:
Outputs:
Frameworks:
POV Statement:
[USER] needs [NEED] because [INSIGHT]
How Might We (HMW):
How might we [action] for [user] so that [outcome]?
Purpose: Generate a wide range of potential solutions.
Key Activities:
Outputs:
Rules for Ideation:
Purpose: Create representations of solutions to explore.
Key Activities:
Outputs:
Prototype Principles:
Purpose: Gather feedback and refine solutions.
Key Activities:
Outputs:
Feedback Framework:
Always start with people and their needs.
Build to think. Don't just talk about ideas.
Diverse perspectives lead to better solutions.
Make ideas tangible early and often.
Use visuals, stories, and prototypes.
Know where you are in the process.
Stay open even when unclear.
| Phase | Time | Focus |
|---|---|---|
| Empathize | 15 min | Quick user perspective |
| Define | 10 min | Problem statement |
| Ideate | 25 min | Solution brainstorm |
| Prototype | 20 min | Concept sketches |
| Test/Feedback | 15 min | Peer review |
| Close | 5 min | Next steps |
| Phase | Time | Focus |
|---|---|---|
| Empathize | 45 min | Deep user research |
| Define | 30 min | Synthesis + HMW |
| Ideate | 45 min | Multiple techniques |
| Prototype | 45 min | Multiple concepts |
| Test | 30 min | User feedback |
| Close | 15 min | Actions |
Extended exploration of each phase with breaks and team exercises.
┌───────────────────────────────────────────────────┐
│ SAYS │
│ (quotes, phrases) │
├───────────────────────┬───────────────────────────┤
│ THINKS │ FEELS │
│ (beliefs, thoughts) │ (emotions, reactions) │
├───────────────────────┼───────────────────────────┤
│ DOES │ │
│ (actions, behaviors) │ │
├───────────────────────┴───────────────────────────┤
│ PAINS │ GAINS │
│ (frustrations, fears) │ (wants, needs, goals) │
└───────────────────────┴───────────────────────────┘
PHASE: Awareness → Consideration → Decision → Use → Loyalty
ACTIONS: [What user does at each stage]
THOUGHTS: [What user thinks]
EMOTIONS: [How user feels - graph line]
PAIN PTS: [Friction points]
OPPTYS: [Opportunities to improve]
HIGH IMPACT
│
┌───────────────┼───────────────┐
│ DO LATER │ DO NOW │
HIGH│ │ │LOW
EFFORT │ EFFORT
│ DON'T DO │ FILL-IN │
└───────────────┼───────────────┘
│
LOW IMPACT
Best For:
Less Suitable For:
See activities.md for detailed activity guides.