Loopify retro
Skill AndreRatzenberger/loopify/plugins/loopify/skills/loopify-retro
Loop yes. Prompt no. Agent skills that turn specs into checked agent loops with receipts.
npx -y skills add AndreRatzenberger/loopify --skill loopify-retroAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use after a loop completes to extract reusable lessons from the contract, trace, final diff, failures, useful checks, ambiguities, and rejected attempts.
SKILL.md
1.4 KB, as published. Nobody here has run it
loopify-retro
Extract lessons from completed loops.
When To Use
- A loop finished.
- Trace data should improve future specs or checks.
- Failures reveal recurring weak spots.
- Rejected attempts contain useful process knowledge.
Do Not Use
- Do not write a generic victory lap.
- Do not promote a project-specific lesson as universal without evidence.
- Do not discard "why not that" knowledge.
Workflow
- Read contract, trace, final diff, and final report.
- Use
references/retro-patterns.mdto classify lessons. - Identify ambiguous spec phrases, useful checks, missing checks, failure clusters, authority surprises, and rejected attempts.
- Write a retro from
templates/loop-retro.md. - Recommend updates to future Loop Contract templates.
- Update memory only when requested or when project rules permit it.
Output
Loop retro document and optional template/process improvements.
Validation
- The retro names checks that mattered.
- The retro names missing evidence.
- Future-template recommendations are concrete.
Example
Use loopify-retro on .loopify/loops/001-papertrail/trace.md and write .loopify/loops/001-papertrail/retro.md.