Run the retrospective over a window of the decision trace — answer eight fixed questions (tier calibration, review signal per sub-agent, recurring failures, diagnosis calibration, spend, chain health, aim calibration, stamp calibration) and turn what recurs into candidate tickets. It is the one skill that reads the trace, and it reads after the fact; it never fixes what it finds and never edits a skill. Use after a wave lands, before a release, or when a wave felt more expensive or more iterative than it should have.
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required retro workflow ingests outsider-authored text without the agent selecting an item: the decision trace's `reason` and `data.*` fields carry PR comment bodies and reviewer words, the batch stamp read fetches every landed ticket's issue body in the window, and the tracker search returns issue titles.
agranado2k/agentic-sdlc
0f5671d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.