菜单
Use when wrapping up work — "done for now", "wrapping up", "end session", "log this", "save progress". Records progress + decisions on the board task and leaves the work clean and resumable by the next session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Apply whenever writing or editing documentation, notes, or knowledge files (vault notes, READMEs, design/architecture docs, changelogs). Enforces rewrite-in-place over append, no contradictions, bounded docs, and no hard-wrapped prose. Shipped and kept current by Loom.
Use when starting a new task, feature, bugfix, or refactor in a Loom project — "let's start", "new task", "working on", "implement", "begin". Ensures a board task exists with a clear scope and a sharp definition of done, then loads context before any code changes.
The operating doctrine for the Loom Platform operator — a friendly, user-facing workspace operator that gets a brand-new user set up and helps maintain their workspace thereafter. Load at the start of any setup-assistant session to help the user create, configure, and archive projects, define agents and profiles, pick default skills and a workflow, and act on their behalf over the curated loom-setup tool surface — confirming big or irreversible actions first. NOT a self-improving Platform Lead.
Use when resuming work or getting up to speed on a Loom task — "pickup", "continue", "what were we doing", "get back to". Reads the project board, recent git history, CLAUDE.md, and (if relevant) your living resume doc to brief the current state and a concrete next step.
The operating doctrine for a Loom lead / orchestrator (manager) session. Load at the start of any orchestrator agent to run the lead-manages-workers loop — plan, decompose, delegate, review, merge, recycle — over the loom-orchestration tools. Your agent prompt supplies the project-specifics; this is the cross-project HOW.
The operating doctrine for the Loom Platform Lead — the standing, human-driven operator ABOVE all projects. Load at the start of any platform-lead session to run the cross-project admin + self-improvement loop (create/maintain projects, agents, profiles and sessions; field manager bug-escalations; own platform-wide concerns) over the loom-platform tool surface. Your agent prompt supplies the platform specifics; this is the cross-project HOW.
| name | loom-session-end |
| description | Use when wrapping up work — "done for now", "wrapping up", "end session", "log this", "save progress". Records progress + decisions on the board task and leaves the work clean and resumable by the next session. |
Leave the work picked-up-able by the next session. The board is the source of truth; the vault holds prose. The daemon auto-commits the vault — never run manual vault git.
tasks_update): note what was completed in the body, record decisions +
their rationale, and add items for what remains. Move the task to its correct column by ROLE
(review / terminal / parked). Only move to a terminal column if it's actually true — scoped work
outstanding means it isn't done.git add <path> …) — never git add -A or git add . in a shared workspace: other unrelated
in-flight work may be present and a blanket stage would sweep it into your commit. Its subject
follows the card's Conventional-Commits title (type(scope): summary). Push with plain git push
(it already refuses a non-fast-forward — there is no valid --ff-only push flag); reach for
--force-with-lease only as a deliberate guard when a force is genuinely intended./loom-doc-hygiene
(rewrite in place, no contradictions, bounded).worker_report — done (one-line summary + key decisions) or blocked
(with needs). Don't merge; your manager reviews and gates. See /worker.recycle_me, seeding the successor from
your living resume doc (worker_recycle is for recycling a subordinate worker, not yourself). See
/orchestrate.Once the board and code are clean, park the session honestly:
end_me (self-terminal).wake_me (a delay + a note) to park it for a later wake rather
than leaving it idle.