skills.rest
barichter
barichterCOMMUNITY
Explore all skills by this author →
GitHub

retro-enforcement

Convert retro action items into GitHub Issues for tracking.

Updated Apr 12, 2026
Search Tags:#productivity#retrospective#GitHub Issues#action item tracking#team process
One-click install
npx skills add https://github.com/barichter/squad --skill retro-enforcement-barichter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro-enforcement
Source: https://github.com/barichter/squad/tree/main/packages/squad-cli/templates/skills/retro-enforcement
Command: npx skills add https://github.com/barichter/squad --skill retro-enforcement-barichter

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that retrospectives are conducted on time and that action items are effectively tracked and completed using GitHub Issues.

Core Features & Use Cases

  • Retro Schedule Enforcement: Checks if the retro has been scheduled and completed within the designated window.
  • Action Item Tracking: Verifies that retro action items are converted into GitHub Issues for better tracking and accountability.
  • Cadence Enforcement: Helps maintain a consistent retro schedule to improve team effectiveness.

Quick Start

Start the retro session using the Invoke-RetroSession command.

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 automatically?▼

Retrospective action items can be tracked in GitHub Issues by converting them directly from the retro session. This Skill verifies that action items are converted into GitHub Issues for tracking and accountability.

What is the best way to enforce a consistent retrospective schedule for my team?▼

Enforcing a consistent retrospective schedule involves checking if the retro has been scheduled and completed within a designated window. This Skill automates cadence enforcement to maintain team effectiveness.

Do I need a specific directory to manage team retrospectives with GitHub Issues?▼

Yes, managing team retrospectives with GitHub Issues requires the .squad/log directory. This directory provides the necessary environment for retro schedule enforcement and action item tracking.

How do I start a retrospective session using GitHub Issues for action item tracking?▼

Start a retrospective session by running the Invoke-RetroSession command. This initiates the retro facilitation process and ensures action items are converted into GitHub Issues.

Can I use GitHub Issues API to automate retrospective action item tracking?▼

Yes, the GitHub Issues API is required to automate retrospective action item tracking. This Skill uses the API to verify that retro action items are converted into GitHub Issues for accountability.

Why does my team need to convert retrospective action items into GitHub Issues?▼

Converting retrospective action items into GitHub Issues improves tracking and accountability. This process ensures that action items generated during retrospectives are effectively monitored and completed.

Related Skills

Explore More Product & Management Skills→
AshleyHollisAshleyHollis

retro-enforcement

Monitor retro schedules and track action items in GitHub Issues.

Community
Intermediate
Ethical-AI-SyndicateEthical-AI-Syndicate
1

retrospective-action-tracker

Track retrospective action items and detect recurring systemic patterns.

Official
Intermediate
DonchitosDonchitos
23.7k

retrospective

Generate sprint retrospective reports from git logs and project plans.

Community
Advanced
nicolehaugennicolehaugen

retro-enforcement

Automate scheduled retrospectives and convert action items to GitHub Issues.

Community
Advanced