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
- 4 months ago
- Last Updated
- 1 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.
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.
retro
Standalone post-④ Verify retrospective workflow — gstack /retro 经验教训 / 决策 / lessons 系统总结 (项目 / 里程碑结束可选, bundled milestone-close retrospective cadence) + planning-with-files RETROSPECTIVE.md 持久化 (sister Phase v2.0-2.5 RETROSPECTIVE pattern)。Capability ref retro-gstack alias suffix per Pattern A E.2 LOCK (NOT bare retro 避免 standalone workflow / capability namespace 冲突)。 schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available (retro-gstack + planning-with-files) + 2 phase (01-retro gstack invoke + 02-persist RETROSPECTIVE.md sink)。Triggered by harnessed CLI `harnessed retro --milestone <name>` or slash command `/retro` after `harnessed setup`.