菜单
Cross-session review — what recurs, what has moved, what has gone quiet, and whether the frame of the issue still fits. Use when the user asks "what keeps coming back", monthly-ish, or before a therapist brief.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/danielrosehill/Claude-Therapy-Workspace-Template --skill thread-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Turn what was said in this session — a dump, a dictated voice memo transcript, or a conversation — into a dated session note, and file it against the threads it belongs to. Use when the user has finished talking and wants it written down, or says "capture this", "write that up".
Close or park this workspace — a retrospective on what changed, what didn't, and what graduates to the persistent background context layer. Use when the user says "I think this is done", or when a review finds the issue has gone quiet for months.
Propose writes back to the persistent background context layer — the non-issue-specific things learned in this workspace. Use at the end of a session, when closing the workspace, or when the user says "remember that".
基于 SOC 职业分类
正在显示 SKILL.md
| name | thread-review |
| description | Cross-session review — what recurs, what has moved, what has gone quiet, and whether the frame of the issue still fits. Use when the user asks "what keeps coming back", monthly-ish, or before a therapist brief. |
The one thing a workspace can do that a conversation can't: look across time.
A thread is something that recurs. threads/<id>.md:
---
type: thread
id: <id>
opened: 2026-07-14
status: open # open | quiet | resolved | archived
sessions: [260714-first, 260801-phone-call]
---
# <the recurring thing, in their words if possible>
## Instances
- 2026-07-14 — <what happened, one line> (sessions/260714-first)
- 2026-08-01 — ...
## What it looks like
The shape, as currently understood. Rewritten when understanding changes;
previous version moved to the History section below.
## What's changed
Movement over time — in the events, or in how they read them.
## History
- 2026-08-01 — description revised: <what changed and why>
threads/, then every session file since the last review (frontmatter threads:
tells you which sessions belong where).context/issue.md still describe what these threads are actually
about? Frames drift, and an unexamined frame is the most common reason a workspace stops
being useful.artefacts/review-YYMMDD.md and update threads/INDEX.md.# Review — 2026-08-14
Covering sessions <first> to <last> (<n> sessions over <period>).
## Open threads
One line each: what it is, how many instances, whether it's moved.
## What's changed since the last review
Concrete differences, not encouragement.
## What's gone quiet
Threads with no instances recently. Say so neutrally — quiet can mean resolved,
avoided, or simply not now.
## What hasn't moved
The honest section. If something has been open for six months and looks the
same, say so plainly and without judgement.
## Frame check
Does context/issue.md still fit? Proposed edits, if any.
## For the next appointment
Anything here worth taking to a professional. Feeds therapist-brief.
archive/ with a line
saying why and when.