/handoff - Agent Handoff

Create a structured handoff between agents with context preservation.

Usage

/handoff [from-agent] [to-agent] [context]

Or interactive mode:

/handoff

Examples

/handoff business-analyst product-owner "Stories ready for prioritization"
/handoff senior-developer qa-engineer "Feature complete, ready for testing"
/handoff architect senior-developer "Technical design approved"

What It Does

1. Captures handoff context:

   • Source agent and work completed
   • Target agent and expected actions
   • Relevant artifacts (tickets, docs, PRs)
   • Key decisions made
   • Open questions or concerns

2. Creates handoff record:

   • Jira comment on related tickets
   • Context package for receiving agent
   • Decision trail update

3. Enables handoff tracking:

   • Links in workflow chain
   • Audit trail
   • Bottleneck identification

Output Format

## Agent Handoff Created

**From:** Business Analyst
**To:** Product Owner
**Time:** 2024-01-15 10:30:00

### Context
Stories created for user authentication feature.

### Work Completed
- [x] Requirements analyzed
- [x] 5 user stories created
- [x] Acceptance criteria defined
- [x] Edge cases documented

### Artifacts
- **Stories:** PROJECT-101, PROJECT-102, PROJECT-103, PROJECT-104, PROJECT-105
- **Documentation:** [BRD - User Authentication](confluence-link)

### Key Decisions Made
1. OAuth2 chosen over custom auth (see ADR-015)
2. Email verification required for new accounts

### For Product Owner
**Expected Actions:**
- Review and validate stories
- Set priorities (MoSCoW)
- Confirm acceptance criteria
- Approve for technical review

**Open Questions:**
- Should social login be included in MVP?
- Password policy requirements from security team?

### Handoff Chain

Stakeholder → Orchestrator → Business Analyst → [Product Owner] → Architect

**Logged to:** PROJECT-100 (Epic), Decision Log

Skill Used

agent-handoff

Integration with Workflow

Handoffs are automatically triggered in workflows:

• Requirements to Stories: BA → PO
• Sprint Planning: PO → Architect → Dev
• Development: Dev → QA → DevOps
• Acceptance: DevOps → PO → Stakeholder

When to Use Manually

Use /handoff when:

• Work completed outside normal workflow
• Explicit context transfer needed
• Returning from escalation
• Cross-team handoffs