retro-enforcement

To automate retro action item tracking in GitHub Issues, this Skill monitors retrospective outcomes and ensures action items are converted into tracked GitHub Issues. It checks scheduling and follow-up completion automatically.

You can enforce team retrospective schedules automatically by running this Skill at the start of every round. It checks if retrospectives are on schedule and coordinates with the .squad/log directory to maintain a structured workflow.

Yes, you need the GitHub API to track retrospective action items. The Skill requires coordination with the GitHub Issues API to ensure action items from retrospectives are successfully converted and tracked.

The best way to ensure retrospective action items are followed up on is using automated schedule enforcement. This Skill checks if retrospectives happen on time and converts their action items into GitHub Issues to improve completion rates.

Yes, you can use this retro enforcement Skill with your existing team workflow. It is designed specifically for team workflows, coordinating with the .squad/log directory to ensure retrospectives are conducted and their outcomes are tracked.

Your retrospective action items might not be tracked if the retrospective schedule is not enforced or if the GitHub Issues API coordination fails. This Skill automates both processes to prevent missing action items and improve completion rates.