retro

Audit sprint retrospective transcripts with DuckDB and generate findings documents.

Updated Mar 10, 2026

Search Tags:#automation #workflow #audit #transcripts #duckdb #sprint #retro

Ready to run

npx skills add https://github.com/iamsteveholmes/momentum --skill retro-iamsteveholmes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/retro
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill retro-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint retrospectives are often manual, opaque, and inconsistent. This skill automates the retrospective auditing process by validating transcript data, verifying story completion, and generating a formal findings document.

Core Features & Use Cases

Transcript audit via DuckDB for sprint sessions
Story verification against done status
Findings document generation and archival
Auditor-team orchestration (documenter + 3 auditors) and guard rails
Sprint closure with actionable story stubs and handoff to intake

Quick Start

Install Momentum retro skill and invoke the retro workflow by running /momentum:retro in your sprint workspace.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate sprint retrospective auditing from meeting transcripts?▼

DuckDB analyzes sprint session transcripts by validating data and verifying story completion against done status. This automated transcript audit replaces manual reviews with deterministic, query-driven checks.

How do I verify story completion status during a sprint retrospective?▼

Verifying story completion during a sprint retrospective checks each story against its done status automatically. The workflow validates transcript data and confirms completion before generating formal findings.

Can I use DuckDB for transcript audits in Agile sprint retrospectives?▼

DuckDB supports transcript audits for sprint retrospectives by querying session data to verify story completion. This integration enables deterministic task orchestration and structured sprint closure actions.

What is the best way to generate formal findings documents from sprint retros?▼

Generating formal findings documents from sprint retros involves orchestrating a documenter and multiple auditors to validate transcripts. The system safely writes retro artifacts and creates actionable story stubs for sprint handoff.

Does automated retro workflow support multi-role auditor orchestration?▼

Automated retro workflows support multi-role auditor orchestration by spawning a documenter and three auditors with built-in guardrails. This structure ensures safe writing of retro artifacts under a clear, deterministic workflow.

How do I handle sprint closure with actionable story stubs and intake handoff?▼

Sprint closure with actionable story stubs and intake handoff finalizes the retrospective by generating formal findings documents. The workflow creates story stubs automatically and passes them to intake for the next sprint cycle.