agf-running-release-retro
SolidUse when product-lead is about to run a release retrospective after a successful MAJOR or MINOR release push (PATCH skipped). Provides applicability gate, pre-conditions, 7-step execution sequence, anti-patterns, and the verification gate before commit. Pairs with template docs/reviews/retro-_TEMPLATE.md and slash /agf-release-retro.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- pcliangx
- Repository
- pcliangx/AppGenesisForge
- Created
- 5 months ago
- Last Updated
- 2 months ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
forge-retro
Run a cycle-completion retrospective after Stage 12 (Release). Synthesizes what went well, what didn't, lessons captured, and pending skill proposals into `pipeline/12-release/retro.md`. Use when the user runs /forge:retro, says "retrospective", "retro", "post-mortem", or asks to close out a release cycle in a Forge project.
release-retrospective
Review how a shipped release, migration or deprecation went against its plan: blast radius, comms, migration, timeline, support load, each gap classed. Triggers: release retro, post-mortem, how did the deprecation go. Planning a new deprecation: deprecation-process.
graph-retro
Post-merge retrospective on the SDLC skill chain (interview-plan → write-plan → execute-plan → review). Reads one ticket's plan and spec, attributes failure signals to the skill that should have prevented them, and proposes one-line amendments. Use after merge and deploy, when the user says "retro this ticket", or when an escaped defect traces to an old ticket. Do not run as the next step after execute-plan or the review.