skills.rest
gaiastudio-ai
gaiastudio-aiOFFICIAL
Explore all skills by this author →
GitHub

gaia-retro

Collect retrospective feedback and write an immutable artifact to docs/implementation-artifacts.

2|Updated Apr 15, 2026
Search Tags:#documentation#retrospective#agile#artifact#sprint#team-collaboration
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gaia-retro
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-retro
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Post-sprint retrospectives are often informal and poorly documented, making it hard to preserve learnings or track action items. gaia-retro provides a guided, write-once workflow that captures went-well, didn't-go-well, and concrete actions and stores a durable artifact in docs/implementation-artifacts.

Core Features & Use Cases

  • Guided, three-section retrospective prompts (went well, improvements, action items)
  • Immutable retro artifacts written to docs/implementation-artifacts and anchored by sprint-id
  • Data-informed facilitation by loading sprint-status.yaml and related story data to seed discussions

Quick Start

Provide sprint-id optionally and initiate the retrospective to produce the artifact at docs/implementation-artifacts/retrospective-{sprint_id}-{YYYY-MM-DD}.md

Frequently Asked Questions about gaia-retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a sprint retrospective with action items?▼

To document a sprint retrospective, this Skill collects went-well, didn't-go-well, and action items, then writes an immutable artifact to docs/implementation-artifacts anchored by a sprint-id.

What is the best way to capture agile retrospective artifacts for my team?▼

The best way to capture agile retrospective artifacts is using a guided, write-once workflow that prevents post-creation edits and preserves a durable record of team feedback.

Can I use existing sprint data to seed retrospective discussions?▼

Yes, the retrospective workflow reads sprint-status.yaml and related story files to load sprint data and seed data-informed retrospective discussions automatically.

How do I start an agile retrospective with a specific sprint-id?▼

To start an agile retrospective, provide a sprint-id and initiate the process to produce a retrospective artifact at docs/implementation-artifacts/retrospective-{sprint_id}-{YYYY-MM-DD}.md.

Are retrospective artifacts immutable once they are written?▼

Yes, retrospective artifacts are immutable and write-once, enforcing a durable record that cannot be altered after the file is created in the implementation artifacts directory.

Do I need a sprint-id to run a retrospective?▼

No, a sprint-id is optional, but providing one anchors the retrospective artifact to a specific sprint cycle for easier tracking and organization within the artifacts directory.

Related Skills

Explore More Software Engineering Skills→
FrancisVargaFrancisVarga

sprint-status

Compute sprint progress tables and risk flags from plan and story files.

Community
Intermediate
phurynphuryn
25.0k

retro

Facilitate structured sprint retrospectives and generate prioritized action items with owners and deadlines.

Community
Intermediate
MarkusonMarkuson

bmad-retrospective

Synthesize development logs and sprint status into retrospective insights.

Community
Advanced
CarlosQ96CarlosQ96

retrospective

Generate sprint or milestone retrospectives from git logs and project plans.

Community
Intermediate