beads-checkpoint

To capture session learnings before ending a development cycle, use a structured wind-down workflow that consolidates activity updates and records them into the issue graph, preventing context loss during handoff.

The best way to prepare a handoff-ready narrative for the next agent is to run a guided session wind-down that summarizes recent activity, verifies graph health, and generates a summary maintaining continuity.

You can update epic and dependency progress at the end of a session by running command-driven guidance within your end-of-session workflow to apply diagnostic updates directly to the beads issue graph.

Session wind-down fails without structured knowledge capture because unrecorded context and unresolved diagnostics are lost, making it impossible for the next agent to maintain continuity or verify issue graph health.

Yes, you can run diagnostics and health checks on the issue graph before handing off by executing integrated beads commands during the wind-down workflow to verify graph integrity and summarize activity.

Yes, you need a SKILL.md file with YAML frontmatter containing the name and description at the root directory to satisfy Skill unit requirements and execute the command-driven wind-down workflow.