skills.rest
Hyeonjun0527
Hyeonjun0527COMMUNITY
Explore all skills by this author →
WebsiteGitHub

retrospective

Execute retrospective steps from a source-of-truth markdown file.

1|Updated Apr 6, 2026
Search Tags:#automation#workflow#documentation#retrospective#agile#process#postmortem
One-click install
npx skills add https://github.com/Hyeonjun0527/yeon --skill retrospective-hyeonjun0527
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/Hyeonjun0527/yeon/tree/main/.codex/skills/retrospective
Command: npx skills add https://github.com/Hyeonjun0527/yeon --skill retrospective-hyeonjun0527

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes the retrospective workflow by delegating execution to a single authoritative source, ensuring consistent practices across teams.

Core Features & Use Cases

  • Authoritative Execution: Reads the source-of-truth document and performs the retrospective steps exactly as defined.
  • Deterministic Workflow: Applies user-provided arguments to the same workflow, preserving intent and context.
  • SSOT Alignment: Keeps behavior aligned with the single source of truth, minimizing drift and customization.

Quick Start

Read the source file ".claude/commands/retrospective.md" and follow its procedure exactly.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I automate a retrospective workflow for an agile team?▼

Standardizing postmortem documentation uses a single source of truth to drive behavior, minimizing drift. It reads the authoritative retrospective procedure file and applies user-provided arguments to maintain deterministic workflow execution.

How do I convert agile retrospectives into preventive actions?▼

Converting retrospectives into preventive actions requires executing documented process steps precisely from an authoritative source. The skill reads the defined procedure and applies user arguments to the same workflow to maintain alignment and context.

What is the best way to standardize postmortem documentation across teams?▼

Standardizing postmortem documentation uses a single source of truth to drive behavior, minimizing drift. It reads the authoritative retrospective procedure file and applies user-provided arguments to maintain deterministic workflow execution.

Do I need a specific source file to run the retrospective process?▼

Yes, you need the source file located at .claude/commands/retrospective.md. The skill reads this file and follows its procedure exactly, using it as the single source of truth to avoid manual edits to the wrapper.

Can I pass custom arguments into the retrospective workflow?▼

Yes, you can apply user-provided arguments to the same workflow. The skill processes these arguments while maintaining alignment with the source-of-truth file, preserving intent and context throughout the execution.

Related Skills

Explore More Software Engineering Skills→
furrycolombia-sysfurrycolombia-sys
1

investigate-error

Automate structured error investigation by following a canonical Claude workflow.

Community
Advanced
IDEA-on-ActionIDEA-on-Action

task-planning

Analyze task data from project documents to identify active work and priorities.

Official
Intermediate
olehsvyrydovolehsvyrydov
13

scrum-master

Facilitate sprint planning, standups, retrospectives, and generate sprint documentation.

Community
Basic
stravineststravinest

codebase-update

Update .codebase documentation to reflect recent code changes.

Community
Basic