Skip to content
managing-handoffs logo

Managing Handoffs

managing-handoffs

Create, update, and archive handoffs with proper metadata and verification

SKILL.md

Full skill instructions

Managing Handoffs

Overview

Manage handoff documents through their full lifecycle: create → work → resolve → archive.

Core principle: Evidence-based verification before closing handoffs.

Announce at start: "I'm using the managing-handoffs skill to [operation]."

Handoff Metadata Template

Every handoff uses this YAML frontmatter:

---
type: handoff
status: active              # active | resolved | archived
created: YYYY-MM-DD
resolved_date: null
archived_date: null
related_sessions: []
related_plans: []
verification:
  implementation_complete: false
  documentation_exists: false
  tests_passing: false
  commits_made: false
---

Operations

Create Handoff

When: Starting new feature work or documenting incomplete work for handoff.

Process:

  1. Get information:

    • Title (brief, descriptive)
    • Description (what needs to be done)
    • Related plans (implementation plan files)
  2. Generate filename:

    from datetime import date
    today = date.today().strftime('%Y-%m-%d')
    slug = title.lower().replace(' ', '-').replace('_', '-')
    filename = f"{today}-{slug}-handoff.md"
    
  3. Create file at: /​docs/​handoffs/​current/​{filename}

  4. Content structure:

    ---
    type: handoff
    status: active
    created: {today}
    resolved_date: null
    archived_date: null
    related_sessions: []
    related_plans: [{plan_paths}]
    verification:
      implementation_complete: false
      documentation_exists: false
      tests_passing: false
      commits_made: false
    ---
    
    # {Title}
    
    **Created:** {today}
    **Status:** 🔴 Active
    
    ## Context
    
    {description}
    
    ## Tasks
    
    - [ ] {task 1}
    - [ ] {task 2}
    - [ ] {task 3}
    
    ## Implementation Notes
    
    [To be filled during work]
    
    ## Completion Criteria
    
    - [ ] All tasks complete
    - [ ] Code committed to git
    - [ ] Documentation updated (guides/​summaries)
    - [ ] Tests passing (if applicable)
    - [ ] Session documented
    
  5. Commit:

    git add docs/​handoffs/​current/​{filename}
    git commit -m "docs: create handoff for {title}"
    

Close Handoff

When: Work is complete and ready to mark resolved.

Process:

  1. Load handoff file

    • Read YAML frontmatter
    • Verify status is 'active'
  2. Run verification checklist:

    Implementation Complete:

    git log --oneline --since="$(yq -r .created handoff.md)" --grep="feat\\|fix\\|refactor"
    
    • Must have commits related to this work
    • Prompt: "Show me the commits for this work"

    Documentation Exists:

    • Check if guide/​summary was created or updated
    • Scan git log for docs/ changes
    • Prompt: "What documentation was created/​updated?"

    Tests Passing (if applicable):

    pytest tests/ -v
    
    • Run relevant tests
    • Must show 0 failures
    • Uses @superpowers:verification-before-completion

    Commits Made:

    • Verify git log shows activity
    • Confirm commits reference the work
  3. Verify all checklist items:

    • If ANY item fails → STOP, cannot close
    • Report what's missing
    • Ask user to complete before closing
  4. Update metadata:

    status: resolved
    resolved_date: {today}
    related_sessions: [{session_files}]
    verification:
      implementation_complete: true
      documentation_exists: true
      tests_passing: true  # or N/​A
      commits_made: true
    
  5. Update status in document:

    • Change Status: 🔴 Active → 🟢 Resolved
    • Add completion date
  6. Move to resolved:

    mv docs/​handoffs/​current/​{filename} docs/​handoffs/​resolved/
    
  7. Commit:

    git add docs/​handoffs/
    git commit -m "docs: resolve handoff - {title}
    
    Verification complete:
    - Implementation: {commits}
    - Documentation: {docs}
    - Tests: {status}
    "
    

Archive Handoff

When: Handoff has been resolved and is ready for archival.

Process:

  1. Verify handoff is resolved:

    • Check metadata: status must be 'resolved'
    • Must be in /​docs/​handoffs/​resolved/
  2. Add RESOLVED- prefix:

    mv docs/​handoffs/​resolved/​{filename} \
       docs/​handoffs/​archive/​RESOLVED-{filename}
    
  3. Update metadata:

    status: archived
    archived_date: {today}
    
  4. Commit:

    git add docs/​handoffs/​archive/
    git commit -m "docs: archive resolved handoff - {title}"
    

List Handoffs

When: Checking project status, finding active work.

Process:

  1. Scan handoffs/​current/:

    find docs/​handoffs/​current -name "*.md" -type f
    
  2. For each handoff:

    • Extract metadata (created date, title)
    • Calculate age (days since creation)
    • Get status
  3. Output format:

    Active Handoffs (3):
    
    1. import-coverage-completion
       Created: 2025-11-13 (2 days ago)
       File: docs/​handoffs/​current/​2025-11-13-import-coverage-completion-handoff.md
    
    2. formula-correction-audit
       Created: 2025-11-13 (2 days ago)
       File: docs/​handoffs/​current/​2025-11-13-formula-correction-audit-handoff.md
    
    3. web-ui-phase-2
       Created: 2025-11-10 (5 days ago)
       File: docs/​handoffs/​current/​2025-11-10-web-ui-phase-2-handoff.md
    

Integration

Uses:

  • superpowers:verification-before-completion - Evidence-based verification

Used by:

  • project-status skill - Shows active handoffs
  • Development workflows - Handoff creation and closure

Common Mistakes

Closing without verification:

  • Problem: Mark resolved without checking verification items
  • Fix: Always run full verification checklist

Missing documentation:

  • Problem: Close handoff without updating guides
  • Fix: Require documentation_exists = true

Archiving active handoffs:

  • Problem: Try to archive without resolving first
  • Fix: Enforce status transitions (active → resolved → archived)

Red Flags

Never:

  • Close handoff without verification
  • Skip test verification if tests exist
  • Archive directly from active status
  • Modify archived handoffs

Always:

  • Run verification checklist
  • Link related sessions and plans
  • Update status atomically
  • Commit each state transition

More skills from majiayu000

xiaohongshu logo
majiayu000/claude-arsenal

xiaohongshu

xiaohongshu

286 148
View
agent-task-conductor logo
majiayu000/claude-skill-registry

agent-task-conductor

Conduct multi-agent task orchestration and workflow coordination.

663 1
View
conductor-setup logo
majiayu000/claude-skill-registry

conductor-setup

Initialize project with Conductor artifacts (product definition,

663 1
View
animation-designer logo
majiayu000/claude-skill-registry

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS

663 1
View
diagramming logo
majiayu000/claude-skill-registry

diagramming

Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...

663 1
View
h3-pg logo
majiayu000/claude-skill-registry-data

h3-pg

PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.

23 1
View
conductor-development logo
majiayu000/claude-skill-registry

conductor-development

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...

663 1
View
conductor-status logo
majiayu000/claude-skill-registry

conductor-status

Display project status, active tracks, and next actions

663 1
View
dockerization logo
majiayu000/claude-skill-registry

dockerization

Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.

663 1
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View