Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
Review a GitHub pull request and post a verdict comment. Stateful — if a previous review comment exists, review only the new commits since the last review and track whether prior findings were addressed. Focus on code cleanliness, duplication, and docs sync. Use when user says "review this PR", "check the PR", "leave…
Classify substantive coding-agent work and shape the full explanation for reviews, explorations, implementations, debugging, planning, research, operations, or general questions. Use when a task begins or clearly pivots; when the user asks Brief-Spec to explain work; or when a Brief-Spec lifecycle hook supplies a type…
Close substantive implementation, investigation, review, or research work with a short, consistently ordered, evidence-backed handoff. Use when a task reaches a terminal outcome; when the user asks what shipped, what changed, what needs attention, or what happens next; or when a host hook requests a valid Brief-Spec…
Re-orient a long, dense, or interruption-prone agent session without replacing the underlying evidence. Use when the user asks for a recap, orientation, simple teaching explanation, or spoken summary; when a session has accumulated many turns or tool calls; before context compaction; or when a Brief-Spec hook says a…
A one-file handoff package for moving a coding task to another person, machine, or work session. It carries checked facts and decisions instead of relying on the old chat history.
Save a compact handoff checkpoint and resume work in a fresh session without replaying the entire transcript via --resume. SAVE trigger — the slash command /handoff-revive:save (carries forward still-relevant goal/decisions/lessons from any existing handoff, then runs a content-quality check). AUTO-SAVE trigger — when…
Save a structured handoff document so another Claude instance (or this one after /clear) can resume the work. Use when context is getting long, switching tasks, or before /clear.
Resume work from a previous session with state verification and git patch restore. Reads the handoff, verifies files and git state, restores patches, and presents a structured briefing.
Capture current session state to a curated artifact at .agent-docs/now/handoff.md plus an archive entry at .claude/handoffs/ - .md. Updates now/status.md, now/work-plan.md, now/open-questions.md, log.md to current reality; sweeps the inter-party obligations ledger both directions (owed-by / owed-to, each receivable…
Prepare a Claude Code project for Codex handoff. Use when the user wants to move work from Claude Code to Codex after rate limits, asks for $ai-handoff FOLDER, wants Codex to read recent Claude conversations, convert CLAUDE.md guidance into AGENTS.md, inspect Claude MCPs/skills/plugins, run a dry-run/apply handoff…
Produce a structured OpenACCP formal report for human owners and downstream agents. Use when reporting project, lane, bootstrap, handoff consume, review, validation, or release-readiness status with progress, gaps, authority limits, and next actions.
Run a bounded OpenACCP Frontier lane. Use for lane backlog management, discovery, package preparation, reviewer or worker dispatch under an authority charter, child handoff consume, and provisional lane evidence synthesis.
Run delegated-final-authority OpenACCP coordination. Use for coordination decisions, authority charters, dispatch, final handoff consume, PR/CI/merge readiness, publication readiness, owner-ready waiver recommendations, and accepting or rejecting reviewed evidence when delegated by charter.
Use when user invokes /handoff-resume, says "pick up where we left off", "continue from last session", "what was I working on", or starts a session with a reference to prior work that may be captured in a previous handoff file.
Use when an auto-compaction system reminder appears, when the user explicitly invokes /handoff or asks to "write a handoff" / "save state", or when the user signals they're near the context limit specifically ("running low on context", "almost out of context", "context is getting full"). Do NOT fire on general…
Write execution-ready Markdown handoffs for Codex /goal runs, including a short goal launcher prompt, authority stack, ordered phases, hard rules, verification gates, and final report requirements. Use when the user asks for a handoff, next-session plan, goal file, /goal prompt, agent execution contract…
Use when leaving a project, joining a project, or performing any project/module handover. Detects .handoff/ directory presence but always confirms intent before acting.
Owner-local responsibility classification and actor lifecycle for a boundary explicitly presented by the aoa-sdk routing control plane or current holder. Use only when that owner invokes this owner-local stage or explicitly re-enters it after compaction, resume, or re-entry; return a typed…