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: 89/100
Skill Content
Details
- Author
- pcliangx
- Repository
- pcliangx/AppGenesisForge
- Created
- 3 months ago
- Last Updated
- 1 weeks ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
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`.
release
Cut an aidemo release: bump package.json, commit, push to main — CI (release.yml) then creates the vX.Y.Z tag, moves `stable`, and publishes the GitHub Release. Use when the user says "cut a release", "release vX.Y.Z", "bump and release", "ship a new version", or "move stable". Knows the gotchas: the version lives ONLY in package.json, pushing a version bump to main IS the ship trigger, CI tagging is idempotent, npm caches the moving `stable` tag (--prefer-online to force-fresh). Do NOT use for: publishing to npm (the engine is npx-from-git only), or installing/updating the skill in consumer repos (that's `aidemo skill update`).
qa-retrospective
Reviews a completed release, incident, project, or testing cycle to identify escaped-risk patterns, process failures, effective controls, and owned preventive actions.