菜单
Structured reasoning strategies (tree-of-thoughts, trilemma, self-consistency, step-back, ReAct). Use when facing complex decisions, weighing trade-offs, comparing multiple approaches, balancing competing objectives, or stuck. `/think <mode>` runs one strategy; `/think` alone shows the menu.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Start the active awareness layer. Launches attend as a persistent Monitor that surfaces environmental changes (git state, peer sessions, process activity) as notifications. Use when the user says "attend", "start awareness", "watch my session", or invokes /attend.
Check how much context window remains in this session — token budget, usage, and room left before compaction. Use when the user asks how much context/room/budget is left, or wants a context-usage gauge.
Land an increment to main through the branch → commit → push → PR → review-gate → merge → cleanup flow. The review gate is a four-square decision (review depth × human gate). Picks up wherever you are in the cycle. Use when the user says "merge this", "land this", "run a review and merge", "ship it", or invokes /merge.
Open a working session — orient to where work was left off, run a structured interview on a greenfield repo, check the context gauge to confirm it's really session-start, then recommend planning with context already warm. The opening bookend to /wrap. Use when the user says "let's start", "pick up where we left off", "what were we doing", "start a session", or invokes /start.
Carry a piece of work through the development loop — pick the loop shape (variable front, stable tail) by where the uncertainty lives, lay the tasklist, then borrow the stage skills rather than reimplementing them. Use when the user says "let's develop this", "work through this feature", "how should we approach this", "what do we do first", or invokes /develop.
Cut a versioned release — infer the version bump, update the changelog, tag, and publish artifacts (GitHub Release, package registries). The heavy sibling of /merge. Use when the user says "cut a release", "publish a release", "tag a version", "ship a release", or invokes /release.
| name | think |
| description | Structured reasoning strategies (tree-of-thoughts, trilemma, self-consistency, step-back, ReAct). Use when facing complex decisions, weighing trade-offs, comparing multiple approaches, balancing competing objectives, or stuck. `/think <mode>` runs one strategy; `/think` alone shows the menu. |
| allowed-tools | Read, Bash, Glob, Grep |
| argument-hint | ["tree|trilemma|consistency|stepback|react"] |
One skill, five structured reasoning strategies. Each surfaces your reasoning
step-by-step instead of jumping to an answer. The think way's metacognitive
check normally escalates here on its own; /think is the manual override —
use it to force an external strategy, choose a specific one, or make
the reasoning visible.
| Mode | Strategy | When |
|---|---|---|
tree | Tree of Thoughts | Multiple viable approaches — branch, evaluate, prune, select |
trilemma | Trilemma | Three competing objectives — satisfice, don't optimize all |
consistency | Self-Consistency | High-stakes — run independent paths, take consensus |
stepback | Step-Back | Stuck — abstract to principles, then apply back |
react | ReAct | Investigation / debugging — reason → act → observe |
/think with no mode: present this table, ask which shape fits the
problem, then run that mode.
Each mode maps to a strategy id (written to the session file) and a definition
file under hooks/ways/meta/think/strategies/:
| Mode | Strategy id | Definition file |
|---|---|---|
tree | tree-of-thoughts | tree-of-thoughts.md |
trilemma | trilemma | trilemma.md |
consistency | self-consistency | self-consistency.md |
stepback | step-back | step-back.md |
react | react | react.md |
1. Session guard — only one think session at a time:
cat /tmp/.claude-think-session 2>/dev/null
If a session is active, ask the user to finish or abandon it before starting another. Do NOT start a second concurrent session.
2. Register the chosen strategy id:
echo "<strategy-id>" > /tmp/.claude-think-session
3. Work the stages. Read the strategy definition and follow its numbered stages in order — present your work for each stage before moving to the next:
cat ~/.claude/hooks/ways/meta/think/strategies/<definition-file>
4. Complete or abandon. After the final stage — or if the user says "never mind" / "skip it" / changes topic — clean up so the think way can fire again for new problems:
rm -f /tmp/.claude-think-session /tmp/.claude-way-meta-think-*"${CLAUDE_SESSION_ID:+-$CLAUDE_SESSION_ID}" 2>/dev/null