handoff-archival

Move old handoffs to archive/ after validating .gitignore safety and git branch activity.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/oduffy-delphi/coordinator-claude --skill handoff-archival
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-archival
Source: https://github.com/oduffy-delphi/coordinator-claude/tree/main/plugins/coordinator/skills/handoff-archival
Command: npx skills add https://github.com/oduffy-delphi/coordinator-claude --skill handoff-archival

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive consumed handoffs by moving files older than 48 hours from tasks/handoffs/ to archive/handoffs/ and checks .gitignore safety. This skill should be used when cleaning up old handoffs, when the handoffs directory is cluttered, or as part of periodic maintenance. Invoked by /update-docs (Phase 8) or standalone.

Core Features & Use Cases

  • Chain-aware archival (supersession pass): Before the time-based sweep, scan all active handoffs for Continuing from references; if the referenced predecessor file is still in tasks/handoffs/, archive it immediately — the successor has absorbed both the predecessor's context (via the preamble) and its unresolved obligations (via the ## Carried Forward section). The predecessor is fully superseded. This pass runs regardless of age.
  • Move old handoffs to archive: Any handoff in tasks/handoffs/ older than 48 hours is a candidate for archival. Before moving, apply the branch-activity check:
  • The 48-hour window ensures multi-session work retains its handoff context — /session-start no longer archives on read, so this is the only archival path. Still concurrent-agent-safe.
  • Do NOT delete archived handoffs — they are the paper trail for why things are written the way they are.

Quick Start

Run the handoff-archival skill via /update-docs (Phase 8) or schedule a maintenance job to clean up old handoffs.

Frequently Asked Questions about handoff-archival

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git workflow archival for stale task handoffs?

Automate git workflow archival by moving handoff files older than 48 hours from tasks/handoffs/ to archive/handoffs/. This process validates .gitignore safety and checks git branch activity before relocating files to preserve active context.

How does supersession work when archiving predecessor handoff files?

Supersession archival works by scanning active handoffs for "Continuing from" references and immediately archiving the predecessor file. The successor absorbs the predecessor's context and unresolved obligations, making the older file fully obsolete regardless of its age.

Why are my old handoff files kept in the tasks directory instead of being deleted?

Old handoff files are moved to an archive directory rather than deleted to maintain a paper trail for audits. Archiving preserves the historical context of why code was written a certain way, while keeping the active tasks directory uncluttered.

When should I avoid archiving handoffs during task management maintenance?

Avoid archiving handoffs when there is recent git branch activity. The archival process checks branch activity against git and keeps handoffs in place if ongoing work is detected, ensuring multi-session work retains its context.

Do I need to check .gitignore before moving old handoffs to an archive folder?

Yes, you need to check .gitignore to ensure the tasks/ directory is not ignored. Validating .gitignore safety prevents archived handoffs from being accidentally excluded from version control and losing the audit paper trail.