agf-running-release-retro

Solid

Use 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.

AI & Automation 480 stars 14 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
89
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Running Release Retrospective Use this skill when: - product-lead has just pushed a MAJOR (`vX.0.0`) or MINOR (`vX.Y.0`) release tag and created the GitHub release - The user typed `/agf-release-retro vX.Y.Z` and the slash dispatched here ## Applicability — PATCH is excluded **Parse `vX.Y.Z`** to gate execution: > retro 是 release 后的**建议复盘(非强制 gate,见 versioning.md step 7)**;本 skill 在用户主动触发 `/agf-release-retro` 时运行。 - `Y=0 ∧ Z=0` → **MAJOR**, retro applies — proceed - `Y>0 ∧ Z=0` → **MINOR**, retro applies — proceed - `Z>0` → **PATCH**, abort with message: "PATCH release — retro not applicable per versioning.md, exiting." If the version is PATCH, do not proceed. ## Pre-conditions All **must pass** before the execution sequence. On any failure, SendMessage product-lead the specific failure and do not proceed: - [ ] CHANGELOG.md contains section `## [vX.Y.Z]`(不再要求"pushed to origin"——下条 `gh release view` 已隐含 release 必须可见于 GitHub) - [ ] `git tag -l vX.Y.Z` returns the tag - [ ] `gh release view vX.Y.Z` returns the release ## Execution sequence ### 1. Copy template and pre-fill header Copy `docs/reviews/retro-_TEMPLATE.md` to `docs/reviews/retro-vX.Y.Z-YYYY-MM-DD.md` (use today's date). Pre-fill: - Title with version and one-sentence release summary - Release date (from git tag annotated date or `gh release view --json createdAt`) - Link to CHANGELOG `[vX.Y.Z](../../CHANGELOG.md)` ### 2. Draft §1 (Progress) Read CHANGELOG `## [vX.Y.Z]` section and any linked PRD / ...

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

AI & Automation Solid

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`.

2 Updated today
easyinplay
AI & Automation Listed

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`).

1 Updated 4 days ago
tandryukha
Testing & QA Solid

qa-retrospective

Reviews a completed release, incident, project, or testing cycle to identify escaped-risk patterns, process failures, effective controls, and owned preventive actions.

1 Updated 3 days ago
SUDARSHANCHAUDHARI