Menú
Structured agent-to-agent handoff. Validates artifact, logs metrics event, dispatches receiving agent.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Behavioral floor management. Propose changes, review proposals, apply approved changes, view status. Routes to COO as behavioral floor guardian.
Compliance program management. Propose changes, review proposals, apply approved changes, audit conformance, view change log.
Generic floor management. Routes to the declared guardian for any governance floor. Use /floor propose <floor-name> <change> to propose changes to any active floor.
Run a retrospective for the last completed work item. Pulls DORA metrics, summarizes flow, captures keep/stop/start.
Interactive project setup: copy templates, configure fleet, define compliance floor, add first specialist agent.
Product Owner commands -- backlog management, prioritization, grooming, review, and status. Routes to the product-owner agent.
| name | handoff |
| description | Structured agent-to-agent handoff. Validates artifact, logs metrics event, dispatches receiving agent. |
| argument-hint | <item> --from <agent> --to <agent> [--urgency blocking|non-blocking] |
Orchestrate a structured handoff between agents as defined in .claude/COLLABORATION.md § Handoff Protocol.
/handoff 42 --from backend-specialist --to security-reviewer -- Send a handoff/handoff 42 --from backend-specialist --to security-reviewer --urgency blocking -- Blocking handoff/handoff complete 42 --from security-reviewer --to backend-specialist -- Complete a handoffParse arguments. Extract item ID, from-agent, to-agent, and urgency (default: non-blocking).
Build the handoff artifact. Prompt the sending agent (--from) to produce a handoff using the COLLABORATION.md format:
**Handoff: [from-agent] -> [to-agent]**
**What was done:** [brief summary of completed work]
**What's needed:** [specific request for the receiving agent]
**Context:** [relevant background the receiving agent needs]
**Artifacts:** [files changed, test results, error logs]
**Urgency:** [blocking / non-blocking]
Feedback prompt. After receiving a handoff, evaluate the sender's work quality. If it warrants behavioral feedback (positive or negative), use ops/feedback-log.sh recommend to propose it to your supervisor.
Validate the artifact. Check that all required fields are present. If any are missing, prompt the sending agent to fill them in. A handoff where the receiving agent would need to ask for clarification is a finding.
Log the event. Run:
ops/metrics-log.sh handoff-sent <item> --from <from-agent> --to <to-agent>
Dispatch the receiving agent. Send the handoff artifact to the receiving agent (--to) with instructions to act on the request.
Capture outcome. After the receiving agent completes, determine: accepted or rejected.
ops/metrics-log.sh handoff-rejected <item> --from <from-agent> --to <to-agent>Parse arguments. Extract item ID, from-agent (the agent completing the handoff), to-agent (the original sender).
Build the completion artifact. Prompt the completing agent to produce a Handoff Complete artifact using the COLLABORATION.md § Handoff Completion format:
**Handoff Complete: [to-agent] -> [from-agent]**
**What was done:** [brief summary of work completed]
**Result:** [success / partial / blocked -- with details]
**Artifacts:** [files changed, test results]
**Follow-up needed:** [yes/no -- what remains]
Note: No metrics event type currently exists for handoff completion. Log the completion as a finding with category "learning" so the event can be tracked. If ops/metrics-log.sh gains a handoff-completed event type in the future, log it here.
Present to user. Show the completion summary. If follow-up is needed, recommend the next action.
| Subcommand | Model | Rationale |
|---|---|---|
/handoff (send) | Sonnet | Structured artifact generation |
/handoff complete | Sonnet | Structured artifact generation |
Implementers can override this skill to add domain-specific handoff checklists. For example, a project might require schema diffs for database handoffs or security scan results for deployment handoffs. Override by creating .claude/skills/handoff/SKILL.md in your project.