retro-enforcement

Automate scheduled retrospectives and convert action items to GitHub Issues.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill retro-enforcement-nicolehaugen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro-enforcement
Source: https://github.com/nicolehaugen/CustomMetricsDashboard/tree/main/.squad/templates/skills/retro-enforcement
Command: npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill retro-enforcement-nicolehaugen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps ensure that retrospectives are conducted on time and that their action items are tracked effectively in GitHub Issues.

Core Features & Use Cases

  • Schedule Enforcement: Monitors and enforces the scheduling of retrospectives.
  • Action Item Tracking: Ensures that all retro action items are converted to GitHub Issues.
  • Use Case: For a team that wants to improve its retro process and boost action item completion rates.

Quick Start

Run the skill at the start of every round to ensure retrospectives are not overdue and action items are tracked.

Frequently Asked Questions about retro-enforcement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce scheduled retrospectives and track missed sessions?

To enforce scheduled retrospectives, this skill monitors log files for missed sessions and automatically initiates retro processes to ensure your team maintains consistent feedback loops and schedule adherence.

How do I convert retrospective action items into GitHub Issues?

Converting retrospective action items into GitHub Issues is automated by this skill, which verifies that every action item generated during a retro session is properly tracked as an issue in your repository.

What is the best way to improve team action item completion rates after retrospectives?

The best way to improve action item completion rates is to enforce retro schedules and automatically convert all action items into tracked GitHub Issues, providing continuous cadence recommendations and monitoring.

Do I need GitHub Issues to track my retrospective action items with this process?

Yes, you need GitHub Issues to track retrospective action items, as this skill specifically verifies action item creation within GitHub and relies on it for improved team feedback loop tracking.

How does retrospective schedule enforcement handle overdue sessions?

Retrospective schedule enforcement identifies overdue sessions by monitoring log files, actively initiating missed retrospectives, and providing cadence recommendations to prevent future scheduling delays.