retro-enforcement

Monitor retro schedules and track action items in GitHub Issues.

Updated May 10, 2026

Search Tags:#retrospective #github issues #agile management #action item tracking #schedule enforcement

Ready to run

npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill retro-enforcement-ashleyhollis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro-enforcement
Source: https://github.com/AshleyHollis/agentic-identity-lab/tree/main/.copilot/skills/retro-enforcement
Command: npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill retro-enforcement-ashleyhollis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires GitHub Issues API, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses the challenge of missing retro action items and low completion rates by ensuring retrospectives happen on schedule and their action items are tracked in GitHub Issues.

Core Features & Use Cases

Schedule Retrospectives: Ensures retrospectives are held on time.
Track Action Items: Automates the creation of GitHub Issues from retro action items.
Use Case: By integrating this skill into your team's workflow, you can maintain a high completion rate for retro action items, leading to better team performance and continuous improvement.

Quick Start

At the start of every round, check for overdue retrospectives with the retro-enforcement skill.

Frequently Asked Questions about retro-enforcement

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

FAQPage Schema

How do I track retrospective action items in GitHub Issues?▼

Tracking retrospective action items in GitHub Issues involves automatically creating issues from retro outcomes to ensure tasks are logged, monitored, and enforced for completion rather than lost in meeting notes.

What is the best way to enforce scheduled retrospectives for agile teams?▼

Enforcing scheduled retrospectives requires monitoring adherence to retro schedules and validating sessions, ensuring agile teams hold retrospectives on time to drive continuous improvement and maintain team performance.

How do I automate the creation of GitHub Issues from agile action items?▼

Automating GitHub Issue creation from agile action items requires integrating schedule enforcement logic with the GitHub Issues API to validate retro sessions and automatically generate tracking tickets for identified tasks.

Do I need a specific directory structure to track agile retrospectives?▼

Yes, tracking agile retrospectives requires a `.squad/log/` directory alongside GitHub Issues API access to validate and manage retro sessions and their associated action items.

Why do retrospective action items have low completion rates in agile management?▼

Retrospective action items have low completion rates in agile management when retrospectives are missed or action items are not tracked in GitHub Issues, leading to lost tasks and lack of continuous improvement.