Retro Resolve
Productivityretro-resolveRetro Resolve is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Scan retro.md files across all skills, resolve open issues, and update retro entries.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/workflow/retro-resolve/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/retro-resolve, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Purpose
Batch-process open retro issues across all skills. Reads each status: open entry, investigates the root cause, applies the fix, and updates the retro entry.
Arguments
--skill <name>— Only process issues for a specific skill (default: all skills)--dry-run— Report open issues without applying fixes
Workflow
1. Discover
Glob for **/retro.md in the skills directory. Parse each file for entries containing status: open.
2. Report
Print: "Found N open issues across M skills" with a summary table.
If --dry-run, stop here.
3. Resolve (sequential by skill)
For each open entry:
- Read context — read the skill's SKILL.md and any referenced files
- Read the retro entry — understand context, root-cause, and resolution-hint
- Investigate — determine the fix (read relevant code, templates, references)
- Apply the fix — edit SKILL.md, template, or reference file
- Update the retro entry:
- Replace
status: openwith a description of what was changed - Add
files-changedlisting modified files - Append
(resolved by /retro-resolve YYYY-MM-DD)to the fix line
- Replace
4. Summary
Print a table listing each issue, its skill, and resolution status (fixed / skipped / needs-review).
Constraints
- Do not change skill behavior or semantics — only fix gaps, errors, and omissions
- If a fix would change behavior significantly, leave the entry open and add a review note
- Process issues sequentially within each skill (related issues may interact)
- Always read the skill's SKILL.md before attempting a fix