CtrlK
BlogDocsLog inGet started
Tessl Logo

retro

Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/retro/SKILL.md
SKILL.md
Quality
Evals
Security

/retro

Analyze retrospective data for recurring themes, sentiment trends, and action item effectiveness.

Usage

/retro analyze <retro_data.json>                             Full retrospective analysis

Input Format

{
  "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

Repository
alirezarezvani/claude-skills
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.