skills.rest
Leep-GH
Leep-GHCOMMUNITY
Explore all skills by this author →
GitHub

Retro Enforcement

Convert retro action items into GitHub Issues at round start.

Updated Apr 16, 2026
Search Tags:#workflow#coordination#enforcement#squad#github-issues#retro
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill retro-enforcement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Retro Enforcement
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/packages/squad-cli/templates/skills/retro-enforcement
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill retro-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure retrospectives happen on schedule and that their action items are tracked in GitHub Issues — not markdown checklists.

Core Features & Use Cases

  • Enforces cadence for retrospectives and blocks other work if a retro is overdue.
  • Converts retro action items into GitHub Issues for visibility, assignment, and completion tracking.
  • Use Case: When a retro results in action items, automatically convert them to issues and ensure owners are notified.

Quick Start

Run Retro Enforcement at the round start to ensure retros are captured as GitHub Issues 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 convert retro action items into GitHub Issues instead of markdown checklists?▼

Running retro enforcement at round start converts action items into GitHub Issues automatically. It blocks other squad workflow tasks until overdue retros are documented, action items are tracked as issues, and completion is verified.

How do I enforce a retrospective cadence and block squad workflow when a retro is overdue?▼

Apply enforcement at the coordinator round start across your squad workflow to enforce retrospective cadence. This detects overdue retros, blocks other work, spawns a facilitator, and resumes normal rounds only after tracking is verified.

What is the best way to track retrospective action items for visibility and completion?▼

Converting action items into GitHub Issues is the best way to track retrospectives for visibility and completion. This assigns owners, enables completion tracking, and verifies action items are resolved before resuming normal squad workflow rounds.

Can I use squad workflow coordination to detect overdue retros and spawn a facilitator automatically?▼

Yes, squad workflow coordination can detect overdue retros and spawn a facilitator automatically. Running enforcement at the coordinator round start guarantees timely retro documentation by blocking work until action items become GitHub Issues.

Why use GitHub Issues for retrospective action items instead of markdown checklists?▼

GitHub Issues provide visibility, assignment, and completion tracking for retro action items, unlike markdown checklists. Enforcement blocks squad workflow rounds until items are tracked as issues, ensuring owners are notified and completion is verified.

Related Skills

Explore More Product & Management Skills→
nicolehaugennicolehaugen

retro-enforcement

Automate scheduled retrospectives and convert action items to GitHub Issues.

Community
Advanced
AshleyHollisAshleyHollis

retro-enforcement

Monitor retro schedules and track action items in GitHub Issues.

Community
Intermediate
barichterbarichter

retro-enforcement

Convert retro action items into GitHub Issues for tracking.

Community
Intermediate
YomiamyYomiamy
16

gen-pr

Generate Markdown PR descriptions from GitHub branch names and issues.

Community
Advanced