retro-weekly

Use this skill at the end of each week or sprint cycle.

Retro Flow

1. Collect delivery evidence (completed work, merged changes, major tasks).
2. Summarize quality signals (bugs, regressions, flaky tests, incidents).
3. Identify process bottlenecks and recurring blockers.
4. Propose concrete changes for next cycle.
5. Confirm owners and next actions.

Output Template

• Wins
• Problems
• Root causes
• Action items
• Carry-over risks

Keep the retro actionable and specific; avoid generic observations.