Analyze sprint artifacts and git logs to generate retrospective reports.
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill retrospective-wsman
Please help me install this Agent Skill. Skill: retrospective Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/retrospective Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill retrospective-wsman
This Skill turns completed sprint or milestone work into a clear retrospective, so teams can understand what shipped, what slipped, what blocked progress, and what to change next.
Ask the retrospective skill to analyze sprint 5 and draft a retrospective with metrics, blockers, trends, and next-step actions.
High-intent search queries and answers about installing and using this skill.
Sprint retrospective analysis compares planned tasks against actual git log commits and repository artifacts. This process produces completion metrics, carryover analysis, estimation accuracy, and actionable recommendations for the next iteration.
A milestone retrospective report includes completion metrics, carryover analysis, scope changes, blocker reviews, and velocity trends. It also evaluates estimation accuracy and identifies technical-debt signals by analyzing TODO and FIXME patterns in the codebase.
Yes, you can analyze estimation accuracy and velocity trends by comparing prior sprint artifacts and planned work against actual deliverables. This requires reading project plans and prior retrospectives to measure performance and identify process improvements.
Yes, retrospective analysis detects technical-debt signals by scanning for TODO and FIXME patterns in the repository. It reviews these code-comment trends alongside blockers and velocity metrics to recommend process improvements for the next iteration.
The best way to identify blockers and carryover is analyzing completed sprint work against actual commits and deliverables. This comparison measures completion, reveals scope changes, and produces actionable next-iteration recommendations for sprint closeouts.
Yes, generating engineering process audits requires reading project plans, git logs, and prior retrospectives. Comparing these planned tasks against actual delivery provides the metrics and carryover analysis needed for actionable audit results.
tkstangMap Git commits to planned tasks and update OAT tracking artifacts.
scomofoGenerate sprint or milestone retrospectives from plans, status, and git history.
nextflow-ioDetect and categorize TODO and FIXME comments in Markdown, Nextflow, and config files.
luanrodriguesGenerates evidence-based delivery status reports by analyzing repository data against a roadmap.
