メニュー
End-of-session documentation reconcile. Runs the Curator to propose a short ADD/RETIRE/PROMOTE list, waits for the human to accept or reject, then runs the Librarian to apply only the survivors. Invoke as /wrap when finishing a working session. User-invoked; never auto-run.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Browser-reviewable L1 acceptance-spec planning for non-trivial code or data changes. Use when the operator asks for planboard, a plan they can annotate in the browser, or a spec of "what must be true and how we verify it" before code. The Orchestrator runs a GQM intent interview, elicits requirements each fused to an acceptance gate, hardens every gate with a mutation-style attack via Codex sub-agents, then renders an annotatable HTML spec. Do not use for trivial one-file edits, quick questions, or research/docs tasks whose success has no writable verifier.
Verifier-Driven Development (VDD) workflow for non-trivial implementation, rewrite, refactor, simplification, data-pipeline, exporter, adapter, prompt, UI preview, training-format work, failure investigation, review feedback, and completion claims. Use when Codex needs to turn operator intent into explicit contracts, mocks, code verifiers, sub-agent verifier passes, and layered validation before, during, or after code changes.
检查和清理中英文文本里的 AI 套路，适用于“去 AI 味”“说人话”“自然一点”“别像模板”“先标问题”这类改写和审稿需求；按场景控制力度，同时保留事实、术语、语域和责任主体。
At session wrap-up, read the session and the docs and propose a short list of changes — what to ADD (things the human flagged out loud), what to RETIRE (now stale or duplicated), and what has earned a guardrail (PROMOTE to a hook, lint, or code structure). The Curator judges and proposes; the human accepts or rejects; the Librarian applies the survivors. It never reorganizes or deletes unattended.
Apply the doc changes the human accepted and keep the documentation findable — relocate prose into the right doc, maintain docs/README.md as the index, write the pointers and hooks that make a doc reach an agent at the right moment, and apply small accepted lints. Runs after the Curator. It organizes and wires; it never judges what's worth keeping (the Curator's job) and never loses information.
| name | wrap |
| description | End-of-session documentation reconcile. Runs the Curator to propose a short ADD/RETIRE/PROMOTE list, waits for the human to accept or reject, then runs the Librarian to apply only the survivors. Invoke as /wrap when finishing a working session. User-invoked; never auto-run. |
A working session adds knowledge and outdates some of what's written; /wrap closes that loop while it's fresh. Two sub-agents run in order with your judgment between them — the Curator proposes, you accept or reject, the Librarian applies. Nothing touches a doc without your accept. Run it from the repo root at the end of a session.
/wrap is a sub-agent workflow. The main agent must keep transcript scanning,
doc archaeology, and doc editing out of its own context.
Use the project custom agents:
wrap-curator for proposal work.wrap-librarian for accepted-item application.If Codex cannot spawn those custom agents, stop and report the blocker. Do not inline the Curator or Librarian work in the main agent as a fallback.
Dispatch ONE wrap-curator sub-agent. Its custom agent config owns the detailed
Curator manual. It reads this session's transcript and the docs and returns a
short list in three moves:
scan_dead_refs.py).Show its list back verbatim, numbered, grouped by move — one line per action. Apply nothing yet. This list spends the scarce thing here, your attention, so pass it on as short as the Curator made it; don't pad it with your own inferred extras.
Wait for the human. They reply by number — 1,3, all, none, or a tweak (2 but file it under docs/foo.md). Don't infer past what they said: a line they didn't accept is dropped, and silence on a line means drop it. Sparse beats wrong — most of all for RETIRE, where a wrong cut costs more than a missed one.
Dispatch ONE wrap-librarian sub-agent, handing it only the accepted items.
Its custom agent config owns the detailed Librarian manual. It relocates prose
into the doc that owns the topic, keeps docs/README.md and
.codex/hooks/doc-map.json in sync, runs the bundled add_doc_link.py /
add_lint.py for any accepted wiring, and flags any code-structure promotion
for you to build deliberately. It relocates and wires; it never drops unique
information.
Close with one short summary of what landed — and, if the Curator flagged a code-structure promotion, say it's waiting on you.
Curator → human → Librarian, every time. The Librarian runs last so the session ends tidy, and each next /wrap's Curator inherits clean ground. If the human accepts nothing, say so and stop — an empty wrap is a fine wrap.