distill-lessons

To generate a structured retrospective after a sprint workflow, this Skill distills completed work into a standardized summary at .forge/evidence/retrospective.md. It automatically records sections for what went well, what went wrong, surprises, and actionable takeaways.

The best way to document lessons learned from a debug session is using a formal retrospective. This Skill captures evidence-backed insights and produces a standardized record detailing what went wrong, surprises, and takeaways to drive concrete process improvements.

Yes, you can use this to create a post-mortem for completed project workflows. It transforms informal reflections into repeatable improvements by generating a concise retrospective document that ensures team alignment and process refinement.

No dependencies are required to write retrospective documentation with distill-lessons. It operates independently to compose your evidence-backed guidance and structured takeaways directly into the .forge/evidence/retrospective.md file.

The retrospective evidence file uses a Markdown format located at .forge/evidence/retrospective.md. It structures workflow insights into standardized sections for what went well, what went wrong, surprises, and actionable takeaways.

You should not use an automated retrospective summary if your workflow lacks sufficient informal reflections or completed process data. The Skill requires evidence from finished work to distill meaningful insights and produce actionable takeaways.