Skip to main content

/handoff - Session Handoff Generator

Generate comprehensive handoff documentation for team members or future self.

System Prompt

EXECUTION DIRECTIVE: When the user invokes this command, you MUST:

  1. Invoke session-summarizer agent for session analysis
  2. Query /cxq for recent work logs and decisions
  3. Check /blockers for current impediments
  4. Review /momentum for activity context
  5. Generate structured handoff document
  6. Optionally save to file or context DB

Usage

/handoff [options]

Examples

# Generate handoff for current session
/handoff

# Save handoff to file
/handoff --save handoff-2026-01-03.md

# Generate handoff for specific track
/handoff --track A

# Include all blockers detail
/handoff --blockers

# Generate for team member
/handoff --to "frontend-dev"

# Quick end-of-day summary
/handoff --eod

What It Does

  1. Summarize Session - Invoke session-summarizer agent
  2. Gather Work Logs - Query /cxq for recent activity
  3. Identify Blockers - Run /blockers for impediments
  4. Check Momentum - Get activity hot spots
  5. Generate Document - Create structured handoff
  6. Store Context - Save to context DB for future reference

Handoff Document Format

# Handoff Document
**Generated:** 2026-01-03 17:30 UTC
**From:** Current Session
**To:** Next Session / Team Member

---

## Executive Summary
Brief 2-3 sentence overview of session accomplishments and state.

## Accomplishments
- [x] Completed cart API implementation (Track A.3)
- [x] Fixed authentication token refresh bug
- [x] Added 15 new unit tests

## Work In Progress
| Task | Progress | Next Action |
|------|----------|-------------|
| Checkout flow | 70% | Complete payment validation |
| User dashboard | 40% | Add chart components |

## Blockers
| Blocker | Impact | Resolution Path |
|---------|--------|-----------------|
| Staging DB timeout | Can't test API | Increase pool size |
| Missing API keys | Can't test payment | Request from DevOps |

## Key Decisions
1. **JWT for authentication** - Better scalability
2. **Retry with backoff** - Handle transient failures

## Momentum
- **Hot areas:** backend/api/, frontend/hooks/
- **Stalled:** devops/terraform/

## Files to Review
| File | Why |
|------|-----|
| `cart.py:150-200` | New endpoint logic |
| `useAuth.ts:45-80` | Token refresh fix |

## Environment State
- Branch: `feature/cart-api`
- Deployed: staging v1.2.3
- Tests: 95% passing (2 flaky)

## Next Steps (Priority Order)
1. Complete checkout payment validation
2. Fix flaky tests in CI
3. Review PR #234

## Context for Cold Start
If starting fresh, begin with:
1. Read `PILOT-PARALLEL-EXECUTION-PLAN.md`
2. Check out branch `feature/cart-api`
3. Run `/work-next` for recommendations

---
*Generated by CODITECT Work Discovery System*

Options

OptionDescription
--save FILESave handoff to markdown file
--track LETTERFocus on specific track
--blockersInclude detailed blocker analysis
--to RECIPIENTCustomize for specific recipient
--eodEnd-of-day quick summary format
--jsonOutput as JSON
--no-contextDon't store in context DB

Data Sources

SourceWhat It Provides
session-summarizerSession analysis
/cxqWork logs, decisions
/blockersCurrent impediments
/momentumActivity hot spots
git statusUncommitted changes

Integration

Works with:

  • session-summarizer - Primary analysis engine
  • /work-log - Source of activity data
  • /blockers - Impediment information
  • /momentum - Activity context
  • /cx - Stores handoff in context
CommandRelationship
/work-nextHandoff informs recommendations
/work-logSource of activity data
/blockersBlocker information
/momentumActivity context
/exportRaw session export

Success Output

When handoff generation completes:

✅ COMMAND COMPLETE: /handoff
Type: <full|brief|eod>
Sections: Activities, Decisions, Blockers, Next Steps
Stored: context-storage/handoffs/

Completion Checklist

Before marking complete:

  • Session data analyzed
  • Handoff document generated
  • Stored in context (unless --no-context)
  • Output displayed

Failure Indicators

This command has FAILED if:

  • ❌ Session summarizer unavailable
  • ❌ No session data to summarize
  • ❌ Context storage write failed
  • ❌ Template rendering error

When NOT to Use

Do NOT use when:

  • Session just started (no data yet)
  • No significant work done
  • Continuing same work immediately

Anti-Patterns (Avoid)

Anti-PatternProblemSolution
Skip at end of dayLost contextAlways run before stopping
Generic handoffUseless infoInclude specific blockers/decisions
Ignore recipientWrong detail levelUse --to for audience

Principles

This command embodies:

  • #6 Clear, Understandable - Structured handoff format
  • #9 Based on Facts - Uses session data
  • #3 Complete Execution - All sections generated

Full Standard: CODITECT-STANDARD-AUTOMATION.md


Version: 1.0.0 Created: 2026-01-03 Author: CODITECT Team