一键导入
ttyl
End-of-session housekeeping. Updates decisions.md and in-progress.md for the current project so the next session can pick up cleanly without --resume.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
End-of-session housekeeping. Updates decisions.md and in-progress.md for the current project so the next session can pick up cleanly without --resume.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Go from ignorance to vague familiarity across a whole name-dropping domain — "just deep enough to hurt." The breadth-first sibling to /study: point it at a domain you don't know (often just a name), and it researches the terms worth recognizing, teaches them in batched 1-2-paragraph lessons with a quiz per item, and leaves a durable one-line-each summary you re-skim before the room. Recognition, not reconstruction. Replaces "three hours on Google." Distinct from /study (deep, one system, reconstruct-under-pressure) and /refresh (re-warm what you already learned). Usually user-invoked; agent may suggest it when "make sure I recognize these next time" intent appears.
Assess the current state of a feature, system, or area. Produces a durable assessment doc that downstream skills (/draft, /plan) can consume. Use --capacity to include napkin math (QPS, storage, bandwidth).
Create a working design document for collaborative iteration. Use when scoping a feature, system change, or workflow — the doc is the conversation artifact, not a summary.
Session startup. Walks the .meta/ tree to load user and domain context, orients to the current project, and gives a brief status summary so we can hit the ground running.
Lightweight session start — the sparse floor below /hello. Does a minimal tree walk (signpost-flag inheritance + root WORKFLOW.md) then reads the local .meta/ — but no full state read and no network. Auto-escalates to /hello for domain/neighborhood/full-state context; never runs MCP/API/calendar or hello.check. Use when you want to get moving fast without the full orientation.
Pre-merge review. Diffs the session's work against the base branch, resolves its review dimensions (configurable via signpost `review.dimensions`/`extra-dimensions`, else inferred from the medium — code default: bugs/efficiency/redundancy/architecture — with `redundancy` the recommended-but-configurable example), always runs the structural dimensions (design/track/merge reconciliation), then presents fixes for approval before committing.
| name | ttyl |
| description | End-of-session housekeeping. Updates decisions.md and in-progress.md for the current project so the next session can pick up cleanly without --resume. |
Session wind-down. Run this before ending a session.
State dir convention: Always write to .meta/, creating it (and subdirectories) if needed.
Silently review:
decisions.md and in-progress.mdAppend any decisions made this session that aren't already logged. Follow the existing format (date + decision). Only log decisions that would be useful context for a future session — not every micro-choice. Check what's already in the file first — /ship and other skills may have already appended entries this session.
Rewrite the Active and Parked sections to reflect current reality:
roadmap.md, not here — in-progress.md
is present-tense onlyIf breadcrumbs.log exists in the state dir:
## Notes): clear it.
Now that decisions.md and in-progress.md are updated, it's redundant.## Notes section: increment every note's session counter by 1.
If any notes have a counter of 5 or higher (they were surfaced in
/hello and still not addressed), delete them silently and print:
"Notes cleared: [list]". Leave all other notes in place.Don't delete the file — the hook expects it to exist.
Check inbox/ for files consumed this session — content folded into a
design, decision, or skill, or explicitly resolved. Move them to
archive/inbox/ per the archival convention (references/archival.md).
Report what was archived; ask before archiving anything ambiguous.
Screenshots (SII files, e.g. *.png) are usually throwaway once acted on.
Default: delete consumed screenshots rather than archive them. The
archive-screenshots: true signpost flag opts into keeping them.
Don't touch todo.md itself — it's the standing item-inbox, not a consumed
file. (Completed todo items graduate via /triage or /review.)
Check designs/ for any accepted designs whose work appears
complete (based on git log and in-progress.md). If found, remind the
user — they may want to run /review to formally close them before ending.
Don't block on this.
Show the user what you wrote/changed so they can adjust before the session ends.