Create and update HANDOFF.md with structured handoff sections at the project root.
npx skills add https://github.com/SamyakJhaveri/loam --skill handoff-samyakjhaveri
Please help me install this Agent Skill. Skill: handoff Source: https://github.com/SamyakJhaveri/loam/tree/main/seed/.claude/skills/handoff Command: npx skills add https://github.com/SamyakJhaveri/loam --skill handoff-samyakjhaveri
Use when ending a session with unfinished work, switching context, or preparing for another agent to continue. Write or update a handoff document so the next agent with fresh context can continue this work. NOT for: session notes, commit messages, or PR descriptions — only structured handoffs for agent continuity.
Create or update HANDOFF.md at the project root with sections Goal, Current Progress, What Worked, What Didn't Work, and Next Steps.
High-intent search queries and answers about installing and using this skill.
To create a structured handoff document, you generate a HANDOFF.md file at your project root containing Goal, Current Progress, What Worked, What Didn't Work, and Next Steps. This ensures the next agent can resume work without re-tracing context.
An agent handoff document must include clear sections for Goal, Current Progress, What Worked, What Didn't Work, and Next Steps. This structured content captures the necessary context to prevent context loss during transitions.
You need to write a handoff document when ending a session with unfinished work, switching context, or preparing for another agent to continue. It is explicitly for agent continuity rather than session notes or commit messages.
Saving HANDOFF.md at the project root localizes the transition context, allowing the next agent with fresh context to automatically locate and resume the work without needing to manually re-trace previous progress.
No, this structured handoff approach is not for commit messages, PR descriptions, or session notes. It is strictly designed for generating structured handoffs that ensure seamless transitions and agent continuity across tasks.
The best way to maintain handoff documents is to update the HANDOFF.md file at the project root during every context switch. You prompt for Goal, Current Progress, What Worked, What Didn't Work, and Next Steps to ensure continuity.
cafe3310Generate HANDOFF.md files with goals, progress, and next steps.
einargudnigReads MEMORY.md and git state to summarize pending work.
javiarmestoDocument architectural decisions and session state for Business Central AL extensions.
KemingHeGenerate structured handoff documents with Context, Key Decisions, Next Objectives, Resources, and Constraints.
