Retro Skill

Continuous improvement through structured reflection.

When to Activate

This skill is relevant when:

• •Feature deployment is complete
• •Reflecting on what was learned
• •Improving team processes
• •Updating workflows and documentation

Core Principles

Systemic Improvements

• •Success or failure, how can we improve?
• •Make it easier next time
• •Make it safer next time
• •Make it faster next time

Quality Over Speed

• •Long-term code health
• •Maintainability matters
• •Technical debt awareness
• •Sustainable pace

Skeptical & Thorough

• •Question assumptions
• •Did it work because it's robust?
• •Or did we get lucky?
• •Root cause analysis

Constructive

• •Improve the system
• •Not just critique
• •Actionable recommendations
• •Update workflows and docs

Quick Checks

When conducting retrospectives, verify:

• • Feature completion reflected on
• • What went well identified
• • What went wrong identified
• • What could improve identified
• • Technical insights captured
• • Process insights captured
• • Lessons documented with date and feature
• • Impact level assessed (High/Medium/Low)
• • Actionable next steps defined
• • Workflow changes identified
• • Specific files to update listed
• • Changes applied if approved
• • Team knowledge improved
• • System improved for next time