claude-skills/commands/retro.md
Claude 894fd23334
feat(agents,commands): trigger descriptions + gated workflow upgrades
- 17 root agents gained 'Use when...' trigger descriptions (<=1024 chars);
  cs-product-analyst placeholder body rewritten around real tools
- 21 commands had invalid YAML frontmatter fixed (unquoted inner colons);
  14 commands gained argument-hint; 6 duplicate commands marked with
  canonical-copy sync comments
- /prd: forcing questions + refuse-to-draft gate + required-sections checklist
- /sprint-plan: capacity math + carry-over check + definition-of-ready gate
- /tdd: rebuilt around the real tdd-guide assets with smoke-tested snippets
- cs-senior-engineer repointed from retired release-manager to
  changelog-generator

https://claude.ai/code/session_019AJddAL1NADWMXsy1qNPQF
2026-06-11 03:58:42 +00:00

42 lines
1.1 KiB
Markdown

---
name: retro
description: "Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>"
---
# /retro
Analyze retrospective data for recurring themes, sentiment trends, and action item effectiveness.
## Usage
```
/retro analyze <retro_data.json> Full retrospective analysis
```
## Input Format
```json
{
"sprint_name": "Sprint 24",
"went_well": ["CI pipeline improvements", "Pair programming sessions"],
"improvements": ["Too many meetings", "Flaky integration tests"],
"action_items": [
{"description": "Reduce standup to 10 min", "owner": "SM", "status": "done"},
{"description": "Fix flaky tests", "owner": "QA Lead", "status": "in_progress"}
],
"participants": 8
}
```
## Examples
```
/retro analyze sprint-24-retro.json
/retro analyze sprint-24-retro.json --format json
```
## Scripts
- `project-management/skills/scrum-master/scripts/retrospective_analyzer.py` — Retrospective analyzer (`<data_file> [--format text|json]`)
## Skill Reference
> `project-management/skills/scrum-master/SKILL.md`