What problem does it solve? Development sessions produce decisions and context that fade quickly; this Skill archives each session into a standardized Markdown log so developers can resume work days or weeks later without losing the reasoning behind changes. ## Core Features & Use Cases - Five-Section Template Enforcement: Every session doc contains Background, Changes, Decisions, Known Issues, and Cross-References sections with strict content requirements. - Mechanical Quality Gates: Validates minimum length, filename format (YYYY-MM-DD-topic.md in kebab-case ASCII), date accuracy, single-topic focus, and merge suggestions against existing session files. - Decision Tracking with Alternatives: Requires each decision to list at least one rejected alternative and the reason for rejection, preserving design rationale. - Use Case: After a coding session that refactored the animation pipeline, invoke this Skill to produce a dated session file in .agent/sessions/ capturing what changed, why, remaining issues, and links to related plans and tech docs. ## Quick Start Archive this session's work by writing a session doc following the rd-session-doc template.
