mega-minds
Version:
Enhanced multi-agent workflow system for Claude Code projects with automated handoff management and Claude Code hooks integration
186 lines (144 loc) • 6.21 kB
Markdown
# Handoff Tracking Log
## Overview
This file serves as a template and active log for tracking all agent handoffs in the multi-agent workflow system. Each handoff must be logged here to maintain audit trail and ensure compliance with communication protocols.
## ⚠️ MANDATORY LOGGING REQUIREMENTS ⚠️
**ALL handoffs MUST be logged using the template below**
**LOG ENTRY REQUIRED**: Before agent begins work
**UPDATE REQUIRED**: When handoff completes or encounters issues
## Active Handoff Tracking
### Template for New Handoffs
```markdown
## Handoff #[Number] - [Date/Time]
### Handoff Details
**From Agent**: @[sender-agent]
**To Agent**: @[receiver-agent]
**Task Description**: [Brief description of work being handed off]
**Priority**: [High/Medium/Low]
### Handoff Content
**Context Provided**: ✅/❌ [Complete project background given]
**Requirements Specified**: ✅/❌ [Clear requirements documented]
**Success Criteria Defined**: ✅/❌ [Acceptance criteria provided]
**Dependencies Identified**: ✅/❌ [All dependencies mapped]
**Integration Points Specified**: ✅/❌ [Connection points defined]
**Timeline Established**: ✅/❌ [Expected completion timeframe]
### Protocol Compliance
**Task Tool Used**: ✅/❌ [Proper Task tool invocation]
**Visual Activation Marker**: ✅/❌ [🤖 @agent-name ACTIVE used]
**Full Handoff Template**: ✅/❌ [communication-protocol.md template followed]
**Acknowledgment Received**: ✅/❌ [Receiving agent confirmed understanding]
### Status Tracking
**Handoff Date**: [YYYY-MM-DD HH:MM]
**Acknowledgment Date**: [YYYY-MM-DD HH:MM]
**Work Start Date**: [YYYY-MM-DD HH:MM]
**Expected Completion**: [YYYY-MM-DD]
**Actual Completion**: [YYYY-MM-DD HH:MM]
**Current Status**: [Pending/Acknowledged/In Progress/Completed/Blocked]
**Completion %**: [0-100%]
### Issues & Resolutions
**Blockers Encountered**: [List any impediments]
**Clarifications Needed**: [Items requiring additional information]
**Resolution Actions**: [Steps taken to resolve issues]
### Quality Gate Status
**Code Review**: [Not Required/Pending/Passed/Failed]
**Testing**: [Not Required/Pending/Passed/Failed]
**Security Review**: [Not Required/Pending/Passed/Failed]
**Performance Review**: [Not Required/Pending/Passed/Failed]
### Handoff Outcome
**Work Completed**: ✅/❌
**Quality Gates Passed**: ✅/❌
**Next Agent Identified**: @[next-agent] (if applicable)
**Lessons Learned**: [Process improvements identified]
```
## Example Handoff Entry
```markdown
## Handoff #001 - 2024-01-15 09:30
### Handoff Details
**From Agent**: @project-orchestrator-agent
**To Agent**: @frontend-development-agent
**Task Description**: Create responsive navigation component for SaaS dashboard
**Priority**: High
### Handoff Content
**Context Provided**: ✅ [SaaS project context, user requirements, design system]
**Requirements Specified**: ✅ [Responsive nav, mobile menu, user authentication state]
**Success Criteria Defined**: ✅ [Mobile responsive, accessibility compliant, <100ms render]
**Dependencies Identified**: ✅ [Design assets from UX agent, API endpoints for user data]
**Integration Points Specified**: ✅ [Authentication context, routing system]
**Timeline Established**: ✅ [2 business days]
### Protocol Compliance
**Task Tool Used**: ✅ [Proper invocation with subagent_type: general-purpose]
**Visual Activation Marker**: ✅ [🤖 @frontend-development-agent ACTIVE used]
**Full Handoff Template**: ✅ [Complete template from communication-protocol.md]
**Acknowledgment Received**: ✅ [Agent confirmed understanding and timeline]
### Status Tracking
**Handoff Date**: 2024-01-15 09:30
**Acknowledgment Date**: 2024-01-15 09:35
**Work Start Date**: 2024-01-15 10:00
**Expected Completion**: 2024-01-17
**Actual Completion**: 2024-01-16 16:30
**Current Status**: Completed
**Completion %**: 100%
### Issues & Resolutions
**Blockers Encountered**: Design asset format not compatible with component library
**Clarifications Needed**: Mobile breakpoint specifications
**Resolution Actions**: Coordinated with @ux-ui-design-agent for updated assets
### Quality Gate Status
**Code Review**: Passed (@code-review-agent - 2024-01-16 15:00)
**Testing**: Passed (95% coverage, all tests green)
**Security Review**: Passed (No vulnerabilities detected)
**Performance Review**: Passed (<50ms render time)
### Handoff Outcome
**Work Completed**: ✅
**Quality Gates Passed**: ✅
**Next Agent Identified**: @testing-agent (for integration testing)
**Lessons Learned**: Design assets should be validated for technical compatibility before handoff
```
## Compliance Tracking
### Daily Summary Template
```markdown
## Daily Handoff Summary - [Date]
**Total Handoffs**: [Number]
**Completed**: [Number]
**In Progress**: [Number]
**Blocked**: [Number]
**Protocol Compliance Rate**: [X%]
**Average Handoff Acknowledgment Time**: [X minutes]
**Average Completion Time**: [X days]
**Issues Identified**:
- [Issue 1]
- [Issue 2]
**Process Improvements**:
- [Improvement 1]
- [Improvement 2]
```
### Weekly Analysis Template
```markdown
## Weekly Handoff Analysis - Week of [Date]
**Performance Metrics**:
- Total Handoffs: [Number]
- Success Rate: [X%]
- Average Completion Time: [X days]
- Protocol Compliance: [X%]
**Top Issues**:
1. [Most common issue]
2. [Second most common issue]
3. [Third most common issue]
**Agent Performance**:
- Fastest Average Completion: @[agent-name]
- Highest Quality Score: @[agent-name]
- Most Handoffs Handled: @[agent-name]
**Process Improvements Implemented**:
- [Improvement 1]
- [Improvement 2]
**Recommendations for Next Week**:
- [Recommendation 1]
- [Recommendation 2]
```
## Usage Instructions
1. **Before Starting Handoff**: Create new entry using template above
2. **During Handoff**: Update status and log any issues encountered
3. **After Completion**: Update final status and record lessons learned
4. **Daily Review**: Summarize day's handoffs and identify patterns
5. **Weekly Analysis**: Analyze trends and implement improvements
This tracking system ensures accountability, identifies bottlenecks, and enables continuous improvement of the multi-agent workflow process.