Menü
Compact the current conversation into a handoff document for another agent to pick up.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Create and operate a durable, task-shaped HTML surface when a human needs to understand, inspect, edit, annotate, compare, decide, approve, or triage generated material with an agent. Use for visual review loops, decision sessions, media review, structured editors, reports, plans, batches, and other work that is clearer in an interactive surface than chat.
Run a documented grilling session in claudex with Claude leading the interview and the GPT/Codex-family grill-advisor challenging the opening design tree and auditing the final decisions. Use when the user wants Claude and Codex to stress-test a plan or design together while recording ADRs and domain terminology.
Watch a Quality Run Chapter execute in another session, read-only, and produce an evidence-first evaluation of how the agents behaved against the rules they were given. Use when a human wants a skill change, routing change, or orchestration change tested on a live Chapter and needs an independent record of what actually happened — not the Driver's own account of it.
Run /quality-loop under claudex with quota-aware Claude-spine and Codex-spine profiles. The selected family coordinates and implements while the other family supplies a persistent design advisor and fresh Correctness-vs-Design reviewer. Use for a substantial autonomous system build that needs cross-family scrutiny, explicit session boundaries, and resumable handoffs.
Turn an outcome, optional discovery brief, or existing GitHub Issue into an approved system design, autonomously implemented and adversarially reviewed semantic Chapters, and a human-readable System Story. Use when the user wants agents to build a substantial change while the human reviews architecture and behavior rather than every code diff, invokes /quality-loop, or resumes an active Quality Run.
Coordinate a lead agent, a persistent specialist or adapter, and a durable shared-state surface while keeping the lead thread thin. Use when work spans multiple feedback rounds, must survive compaction or session boundaries, or combines an agent-owned task with a delegated surface, reviewer, researcher, or advisor. Defines agent interaction and continuity; pair with model-orchestration for model selection and atelier for review surfaces.
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it under the workspace's .scratch/ directory (create it if it does not exist) — prefer the relevant feature subdirectory .scratch/<feature-slug>/ when the work maps to one, otherwise .scratch/handoffs/. .scratch/ is gitignored/local-only, so the handoff stays out of version control.
Before writing, list existing *.md files in the target folder to determine the next index: find the highest leading numeric index (e.g. 03- → next is 04), defaulting to 01 if none exist. Name the file MM-DD_<N>_<slug>.md (e.g. 06-25_02_evaluate-refine-loop.md) so multiple handoffs in the same folder sort chronologically then by creation order within the same day.
Open the document with a Created: timestamp on the first line (e.g. Created: 2026-06-25 14:32) so the exact creation time is visible without inspecting file metadata.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
