retro

Automate team retrospectives with gstack and store reports in repositories.

Updated Mar 23, 2026

Search Tags:#project management #retrospective #team review #DNA injection #repo automation

Ready to run

npx skills add https://github.com/disciplin-run-org/jjstack --skill retro-disciplin-run-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/disciplin-run-org/jjstack/tree/main/skills/retro
Command: npx skills add https://github.com/disciplin-run-org/jjstack --skill retro-disciplin-run-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of conducting project retrospectives by automating report storage and DNA injection, enabling consistent and efficient team reviews.

Core Features & Use Cases

Enhanced Retrospectives: Wraps gstack's /retro command with repository-local outputs and DNA injection for tailored session context.
Configuration Loading: Reads project-specific configuration files to customize output directories and DNA paths.
Post-Session Processing: Captures output and manages README updates to reflect recent insights, common in team ICT workflows.

Quick Start

Use the retro skill to initiate a team retrospective that saves reports directly in your project repository and injects relevant contextual DNA.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate team retrospective reports in a code repository?▼

Automating team retrospective reports in a code repository uses gstack integration to capture session outputs and manage README updates directly within your project. This ensures documentation consistency for continuous improvement workflows.

What is DNA injection in the context of project retrospectives?▼

DNA injection in project retrospectives is the process of injecting tailored contextual information into your session. It reads project-specific configuration files to customize output directories and provide relevant context for team reviews.

Do I need specific tools to configure repo-based retrospective automation?▼

Configuring repo-based retrospective automation requires tools like WebSearch, AskUserQuestion, and Bash for execution. These tools facilitate the gstack integration needed to run the retrospective commands and process session outputs.

How does a repository-based retrospective compare to standard team review processes?▼

Repository-based retrospectives differ from standard team reviews by storing outputs locally in the code repository and injecting contextual DNA. This approach wraps existing commands to maintain documentation consistency directly within collaborative development environments.

Can I customize output directories for my project retrospective sessions?▼

You can customize output directories for project retrospective sessions by loading configuration files. The process reads project-specific configuration files to customize where reports are saved and how contextual DNA paths are managed.