agent-handoff-docslisted

# Agent Handoff Docs A documentation framework for development that spans multiple agent sessions, multiple agent products, or agents working alongside humans. The next reader arrives with zero context. What they need is not more documentation — it is documentation whose ownership is unambiguous: every file states what it is the source of truth for, exactly one file states where work stands right now, and everything else can be compressed or deleted without fear of losing the only copy of a fact. The file names used below (REQUIREMENTS, ARCHITECTURE, REPORT, HANDOFF, START_HERE, TASKS) are conventions, not requirements. What matters is that the names are consistent across every repository you maintain, and that each document declares its scope at the top. ## When To Use - Work on a repository spans multiple sessions or is handed between agents (or between agents and humans), and every new session pays a re-discovery cost before producing anything. - Handoff documents keep going stale: dated snapshots pile up, "current state" appears in several files, and no reader trusts any of them. - You are onboarding a new agent onto an existing repository and want one kickoff prompt that works identically across every repository you own. - Implementation ran ahead of documentation and you need to reconstruct requirements after the fact (reverse-engineered requirements). - You are about to restructure a pile of legacy documents and need a target shape plus a safe migration