メニュー
Strategy selector for structured reasoning. Lists available thinking frameworks and invokes the right one. Use when facing complex decisions, trade-offs, or when stuck.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | think |
| description | Strategy selector for structured reasoning. Lists available thinking frameworks and invokes the right one. Use when facing complex decisions, trade-offs, or when stuck. |
| allowed-tools | Bash, Read, Glob |
Explicit invocation of the structured thinking escalation. Use /think when you want to force an external reasoning strategy — the metacognitive check in the think way normally handles this autonomously.
/think # Show available strategies and select one
/think <strategy> # Invoke a specific strategy directly
| Problem Shape | Skill | When to Use |
|---|---|---|
| Multiple viable approaches | /think-tree | "What are the options?" — branch, evaluate, prune |
| Three competing objectives | /think-trilemma | "We can't have all three" — satisfice |
| High-stakes decision | /think-consistency | "Are we sure?" — independent paths, consensus |
| Stuck / need principles | /think-stepback | "Why does this work?" — abstract, then apply |
| Investigation / debugging | /think-react | "Figure out why" — reason-act-observe cycle |
/think ExplicitlyThe think way's escalation gradient (internal → external → collaborative) handles most cases automatically. /think is the manual override.
Think sessions have a lifecycle: start → work stages → complete (or abandon).
Before starting a new session:
# Check for active think session
cat /tmp/.claude-think-session 2>/dev/null
Abandoning a session (user says "never mind", "skip it", changes topic):
rm -f /tmp/.claude-think-session /tmp/.claude-way-meta-think-*"${CLAUDE_SESSION_ID:+-$CLAUDE_SESSION_ID}" 2>/dev/null
After completion or abandonment, the think way can fire again for new problems.
Score way matching (embedding and BM25), analyze vocabulary, and validate frontmatter. Use when testing how well a way matches prompts, checking cosine similarity or BM25 scores, inspecting the embedding engine status, or validating way files.
Check how much context window remains in this session. Use when you want to know token budget, context usage, or how much room is left before compaction. Also use proactively when working on long tasks to gauge remaining capacity.
Cite governance controls and justifications when making recommendations about code quality, security, commits, or documentation. Use when justifying why a practice matters, when a user asks "why do we do this?", when reviewing code against standards, or when recommending practices that align with NIST, OWASP, ISO, SOC 2, CIS, or IEEE controls.
Ship current work through the branch → commit → push → PR → merge → cleanup flow. Picks up wherever you are in the cycle. Use when the user says "ship it", "land this", "merge this", or invokes /ship.
Review what changed in Claude Code upstream and compare against this project's commits and ADRs. Surfaces opportunities, gaps, and ADR status drift. Discovery conversation, not compliance dashboard.
Self-Consistency reasoning — run multiple independent reasoning paths and take consensus. Use for high-stakes decisions where reasoning errors are costly.