メニュー
Use when facing a decision, unclear or recurring problem, system behavior question, communication challenge, or when generating novel solutions — loads structured thinking frameworks
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
OpenCode agent runtime — manage sessions, dispatch tasks, repair DB issues, and reset diffs
Look up people, projects, products, and decisions locally first: contact info (email, Slack ID, GitHub handle), titles and teams, project/product status, who works on what, and past decisions. Check before searching Slack, email, calendar, or GitHub — this is the first stop for any contact detail, project context, or decision-history question.
Load when reviewing a diff, naming a code smell or anti-pattern, deciding refactoring direction, or grading review-comment severity. Required reading when a named pattern is cited — load explicitly rather than paraphrasing from memory.
Load before creating, restacking, or landing a branch in a git-spice–managed stack — branch naming, stack navigation, and conflict/restack recovery. Use instead of raw git commands whenever the repo has a git-spice stack.
Load when investigating production errors, latency, or trace data that requires querying Elasticsearch/APM directly — index patterns, field names, auth setup, and time-range syntax. Use before hand-rolling a query DSL call or guessing field names.
Manage dotfiles via chezmoi — apply safely, destroy files, manage LaunchAgents and externals, config and template gotchas
| name | thinking-tools |
| description | Use when facing a decision, unclear or recurring problem, system behavior question, communication challenge, or when generating novel solutions — loads structured thinking frameworks |
| license | MIT |
Given a situation, identify the right framework category, read the relevant file, and apply it.
| Category | When to use | File |
|---|---|---|
| Problem framing & root cause | Problem is unclear, recurring, or needs reframing | frameworks/problem.md |
| Decision making | Choosing between options, calibrating effort, prioritizing | frameworks/decisions.md |
| Systems thinking | Understanding why a system behaves the way it does | frameworks/systems.md |
| Communication | Writing clearly, giving feedback, resolving conflict | frameworks/communication.md |
| Creative problem solving | Generating novel solutions, exhausted obvious approaches | frameworks/creative.md |
Read the user's situation and pick the best-fit category. If a problem spans two categories (e.g. a decision about a system), read both files.
If the user names a specific framework (e.g. "use inversion" or "cynefin"), go straight to the relevant file — don't re-route.
Use the Read tool on the relevant file path:
~/.agents/skills/thinking-tools/frameworks/problem.md~/.agents/skills/thinking-tools/frameworks/decisions.md~/.agents/skills/thinking-tools/frameworks/systems.md~/.agents/skills/thinking-tools/frameworks/communication.md~/.agents/skills/thinking-tools/frameworks/creative.mdEach file contains multiple frameworks. Pick the most relevant one and apply it. If two frameworks complement each other (noted in "Related Tools"), apply both.