Individual skill
dev-retro
AI DevKit · Run an evidence-based retrospective on finished work (feature, session, incident) and turn friction into durable fixes, automation first. Use when users ask for a retro, lessons learned, post-mortem, or "what went wrong", or when another skill offers one after a feature or fix.
skills/dev-retro/SKILL.md
Source commit d2e170abef698edb63c3a39ba8fce569b6fe4b2c
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,660
- Repository last updated
- Nov 4, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- claude-code Repository topic
- antigravity Repository topic
- agent-skills Repository topic
- agent-framework Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- cli Repository topic
- codex-cli Repository topic
- coding-agents Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,321 bytesagents/openai.yamlasset · 330 bytes
Read excerpt
# Retro
Turn what went wrong into fixes that stop it recurring. Not a status summary: use `session-compact` for handoff state.
## Rules
- When suggested by another skill, ask the user before running; skip silently if declined.
- Every item needs evidence: a failed command, hook or test output, a user correction, a revert, or rework in the diff. No generic lessons.
- Cap at the 3-5 highest-cost items. Note what worked in one line only if it should be kept on purpose.
- Blameless: describe the gap in the system, not the person or agent.
- Never copy secrets, credentials, or personal data from transcripts into fixes or memory.
## Fix Ladder
