Retro Enforcement Skill
Ensure retrospectives happen on schedule and that their action items are tracked in GitHub Issues — not markdown checklists. Published by microsoft in frontier-agentic-devops-rvas.
What is Retro Enforcement Skill?
Ensure retrospectives happen on schedule and that their action items are tracked in GitHub Issues — not markdown checklists. Published by microsoft in frontier-agentic-devops-rvas. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Testing use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use Retro Enforcement Skill
- Use it for testing.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/frontier-agentic-devops-rvas
- Skill file: .squad/templates/skills/retro-enforcement/SKILL.md
What it does
Ensure retrospectives happen on schedule and that their action items are tracked in GitHub Issues — not markdown checklists.
Skill instructions
Skill: Retro Enforcement Purpose Ensure retrospectives happen on schedule and that their action items are tracked in GitHub Issues — not markdown checklists. This skill addresses a specific, measured failure mode: 0% completion rate on markdown retro action items across 6 consecutive retrospectives. GitHub Issues have an 85%+ completion rate in the same squad. The format was the problem, not the people. Core Function: Test-RetroOverdue powershell function Test-RetroOverdue { param( [string]$LogDir = ".squad/log", [int]$WindowDays = 7, [string]$Pattern = "retrospective" ) $cutoff = (Get-Date).AddDays(-$WindowDays) $retroLogs = Get-ChildItem -Path $LogDir -Filter $Pattern -ErrorAction SilentlyContinue | Where-Object { $.LastWriteTime -ge $cutoff } return ($retroLogs.Count -eq 0) } Returns - $true — No retro log found within the window. Retro is overdue. Block other work. - $false — At least one retro log found within the window. Proceed normally. Detection Logic The function checks .squa
Explore related resources
Frequently asked questions
What is Retro Enforcement?
Retro Enforcement is a open-source AI agent skill with Copy skill directory. Ensure retrospectives happen on schedule and that their action items are tracked in GitHub Issues — not markdown checklists.
Who is Retro Enforcement best for?
Retro Enforcement is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows.
How do I install Retro Enforcement?
Install or run Retro Enforcement using Copy skill directory. Check Retro Enforcement for the latest setup command.
Is Retro Enforcement actively maintained?
Retro Enforcement may need a closer maintenance check before production use.
Auto-fetched from GitHub.