csdlc-retro

Append session handoffs to NEXT.md in Foundry journals.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: csdlc-retro
Source: https://github.com/danhannah94/claymore-plugins/tree/main/csdlc/skills/csdlc-retro
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of capturing and persisting session handoffs by appending them to NEXT.md at the end of a CSDLC working session, ensuring continuity and traceability.

Core Features & Use Cases

  • Write the session handoff into NEXT.md in Foundry (status/{username}/next.md or status/next.md for single-user setups). If Foundry is unreachable, fallback to a local NEXT.md and flag for sync on the next session.
  • Maintain a running, historical journal where the most recent session work appears at the top, while prior shipped sections remain as references.
  • Support structured handoffs for review and handoff between agents and humans, enabling consistent handoff quality across sessions.

Quick Start

During the end of a session, trigger the retro workflow to append the latest handoff to NEXT.md.

Frequently Asked Questions about csdlc-retro

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

FAQPage Schema
How do I automate NEXT.md handoffs when a development session ends?

Automating NEXT.md handoffs involves appending the latest session summary to a running journal at session end. This Skill triggers that workflow automatically, capturing session continuity and traceability without manual entry.

What is a session handoff journal and how does NEXT.md maintain it?

A session handoff journal records work continuity between development sessions. NEXT.md maintains this by appending the most recent session work at the top, keeping prior shipped sections as historical references below.

Can I write session handoffs to Foundry journals like status/next.md?

Yes, you can write session handoffs directly to Foundry journals using paths like status/{username}/next.md or status/next.md for single-user setups. The Skill requires Foundry access and a mechanism to update the running journal without compromising history.

What happens to NEXT.md session updates if Foundry is unavailable?

If Foundry is unreachable, NEXT.md session updates fall back to a local NEXT.md file. The local handoff is then flagged for synchronization with Foundry during your next working session.

What's the best way to structure documentation for agent and human handoffs?

The best way to structure handoff documentation is using a standardized NEXT.md journal format. This supports structured handoffs for review between agents and humans, ensuring consistent handoff quality and traceability across all sessions.