work-report

Automating retrospective report generation involves producing a structured markdown file covering task outcomes, decision logs, lessons learned, and action items. This Skill outputs a 9-section markdown report and a concise terminal summary to fully automate post-task documentation.

Documenting decision-making processes and lessons learned is best handled by generating a structured post-task retrospective. This Skill automatically populates a 9-section markdown template capturing confidence levels, technical debt, and skill suggestions for future reference.

Yes, you can generate a concise terminal summary alongside a full markdown report. This Skill outputs a 5-10 line terminal summary for quick review while simultaneously creating the detailed retrospective markdown file for team sharing.

Generating a retrospective report requires adhering to a strict 9-section markdown template. Mandatory sections cover task summary, decision logs, mistakes, plan vs. actual, confidence, learnings, technical debt, skill suggestions, and action items to ensure comprehensive documentation.

A post-task work completion report should include action items, technical debt, and skill suggestions alongside the task summary and decision logs. This Skill automatically structures these elements into the final markdown report to track development improvements.