skills.rest
L3DigitalNet
L3DigitalNetOFFICIAL
Explore all skills by this author →
WebsiteGitHub

agent-handoff

Route repository facts by lifetime and maintain session continuity across agent sessions.

Updated Jun 2, 2026
Search Tags:#documentation#validation#repository#session continuity#agent handoff#closeout#fact routing
One-click install
npx skills add https://github.com/L3DigitalNet/project-standards --skill agent-handoff-l3digitalnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-handoff
Source: https://github.com/L3DigitalNet/project-standards/tree/main/.agents/skills/agent-handoff
Command: npx skills add https://github.com/L3DigitalNet/project-standards --skill agent-handoff-l3digitalnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent sessions lose project context when they end, and durable knowledge gets scattered or lost. This Skill keeps project knowledge inside the repository, routing each fact to a canonical document by lifetime so the next session starts with the right context. ## Core Features & Use Cases - Fact Routing by Lifetime: Directs facts to canonical owners such as docs/STATUS.md for current snapshots, docs/TODO.md for future work, docs/handoff/state.md for in-flight work, and numbered bug records for durable lessons. - Session Startup and Closeout: Defines startup steps that reuse SessionStart-injected context and a closeout workflow that updates status, prunes eager state, appends session records, and validates with the project-standards CLI. - Validation and Migration: Enforces document size caps and structure via validate, drift-check, and shape-check commands, and reconciles legacy handoff layouts through a reviewed local migration process. - Use Case: At the end of a coding session, run the closeout steps to move completed work from state.md into STATUS.md, record a bug lesson, and validate the diff so the next agent session inherits only what it needs. ## Quick Start Use the agent-handoff skill to close out this session by routing current facts to their canonical documents and validating the handoff state.

Frequently Asked Questions about agent-handoff

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

FAQPage Schema
How do I maintain agent session continuity in a repository?▼

Keep project knowledge in repository documents routed by lifetime: eager in-flight state in docs/handoff/state.md, current snapshots in docs/STATUS.md, and durable facts in lazy handoff files. At closeout, prune completed state and validate with the project-standards CLI.

How do I close out an agent session with agent-handoff?▼

Run the delta command with the session-start OID, update STATUS.md and TODO.md, remove completed detail from state.md, append a session record, then run validate and drift-check. Delegate to a closeout subagent when the harness provides one.

Where should different project facts be stored in a handoff layout?▼

Facts route to canonical owners by lifetime: state.md for in-flight work, deployed.md for deployment truth, architecture.md for component graphs, credentials.md for secret references, conventions.md for stable patterns, and numbered bug records for durable lessons.

Can I store credentials or secrets in handoff documents?▼

No. Store only credential references such as secret names, environment variable names, or OpenBao paths in docs/handoff/credentials.md. Passwords, tokens, private keys, and other secret values must never be written to handoff files.

What are the size limits for handoff documents?▼

state.md has a 2048-byte hard cap with a 1740-byte target, STATUS.md targets 60 lines, and other documents have per-bullet and per-paragraph character caps. The validator reports the measured size and applicable maximum, which is authoritative.

How do I migrate an older handoff layout to the current standard?▼

Run the legacy-report command to inventory recognized and unclassified evidence, then preserve useful content, route facts by lifetime, and validate the result. Migration is a reviewed local process, not an automated converter, and ambiguity is preserved for owner review.

Related Skills

Explore More Software Engineering Skills→
fluxforgeaifluxforgeai
3

session-start

Load CLAUDE.md and handoff documents to initialize a new session.

Community
Advanced
All-The-VibesAll-The-Vibes
50

takeoff

Classify backlog tasks into actionable, blocked, in-progress, and ready-to-work categories.

Official
Advanced
shihwesleyshihwesley

obsidian-markdown

Create and edit Obsidian-flavored Markdown notes with wikilinks, embeds, and frontmatter.

Community
Intermediate
arbgjrarbgjr

github-wiki

Sync project documentation and ADRs to a GitHub Wiki.

Community
Intermediate