Generate structured Epic retrospectives and route learnings to steering docs.
npx skills add https://github.com/xiduzo/wtf --skill wtf-retro
Please help me install this Agent Skill. Skill: wtf.retro Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.retro Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-retro
Close out a completed Epic with a structured retrospective to compare what was planned against what shipped, surface deviations, and capture actionable learnings for steering the next initiative.
Initiate a retro on the completed Epic to generate learnings and finalize the Epic summary.
High-intent search queries and answers about installing and using this skill.
Run an Epic retrospective by comparing planned work against shipped deliverables to surface deviations and formalize learnings. The retrospective generates a final Epic summary and routes insights into steering docs like TECH.md, QA.md, DESIGN.md, and VISION.md for future planning.
An Epic retrospective is a structured review comparing original plans to delivered work to capture actionable learnings. You need it during Epic closures, sprint finales, and post-mortems to feed process improvements into steering docs and future initiatives.
Yes, Epic closure integrates changelog generation alongside the retrospective process. After finalizing the Epic summary, you can formalize closure with documented outcomes and route results directly into your changelog and release processes.
Retrospective learnings route directly into steering docs like TECH.md, QA.md, DESIGN.md, and VISION.md. After comparing planned versus shipped work, the process surfaces deviations and feeds actionable improvements into the appropriate documentation for guiding next initiatives.
Use a structured retrospective to compare the original Epic plan against what actually shipped. This surfaces deviations between planned and delivered work, captures actionable learnings, and generates a final Epic summary to formalize the closure with documented outcomes.
Yes, the retrospective process applies to Epic closures, sprint finales, and post-mortems. It compares planned work against shipped deliverables across steering docs, changelog generation, and process improvement to formalize learnings for future planning.
TraftGGenerate a Markdown retrospective from sprint plans and git history.
dianlightRead completed tasks from docs/tasks/ and append entries to CHANGELOG.md.
cenconq25Compare sprint plans to live work and output a drift summary.
boshu2Run a council retrospective and generate a structured post-mortem report.
