Release planning
Skill ahtishamshahzad/agent_dev_flow/.ai/skills/release-planning
Use to validate release readiness and plan a release — tests green, docs and changelog updated, versioning handled, git workflow followed, and any publish/deploy explicitly approved. Enforces Gate 7; never ships on a failed gate.From its SKILL.md
npx -y skills add ahtishamshahzad/agent_dev_flow --skill release-planningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.7 KB, 783 tokens by cl100k_base, as published. Nobody here has run it
Release Planning
Purpose
Validate that work is ready to ship and plan the release safely. Enforces Gate 7 (../../system/QUALITY_GATES.md) and follows ../../system/GIT_WORKFLOW_RULES.md. Publishing/deploying is outward-facing and requires approval.
When to Use
- For a release or deployment request type.
- Before shipping any completed, reviewed work.
- Not to publish/deploy without explicit approval or a passed gate.
Inputs
- The reviewed, tested change set.
- Version/changelog state; release criteria.
- Deploy target and approval status.
Discovery Questions
- Are tests green and reviews complete (Gates 5–6)?
- Is the changelog/version updated?
- What is the deploy target and rollback plan?
- Has the user approved the publish/deploy step?
Responsibilities
- Verify release criteria: tests green, security/quality review done, docs + changelog updated, version handled.
- Confirm git workflow followed (branch/PR/merge state).
- Plan the release/deploy with a rollback path.
- Ensure any publish/deploy step is explicitly approved.
- Record the release decision and outcome.
Required Workflow
- Confirm Gates 5–6 passed.
- Verify docs, changelog, and version are updated.
- Confirm git state (merged/tagged as required).
- Confirm explicit approval for publish/deploy.
- Execute (or hand off) the approved release with a rollback plan.
- Verify and record the outcome.
Decision Rules
- Do not ship on a failed gate — stop and report.
- Publish/deploy is outward-facing → explicit approval required.
- No release without a rollback path for risky changes.
- Version/changelog updates precede tagging.
Rules
- Gate 7 is mandatory; a green build alone is not release readiness.
- Follow
../../system/GIT_WORKFLOW_RULES.mdfor tags/branches. - Never expose secrets in release artifacts (
../../system/SECURITY_RULES.md).
Anti-Patterns
- Shipping with failing/absent tests.
- Deploying without approval or rollback.
- Skipping changelog/version.
- Treating a passing CI as sufficient proof of readiness.
Validation Checklist
- Gates 5–6 passed.
- Docs + changelog + version updated.
- Git state correct (merged/tagged).
- Rollback plan for risky changes.
- Publish/deploy explicitly approved.
- Outcome verified and recorded.
Definition of Done
Release readiness is validated (Gate 7): tests green, reviews done, docs/changelog/version updated, git state correct, rollback planned, publish/deploy approved and verified — or the release is blocked with a clear reason.
Related Skills
git-workflow, github-repository, testing-strategy, security-review, final-quality-audit, migration-planning (cutover), project-orchestrator.
Related Knowledge
../../knowledge/ (deploy targets, environments).
Related References
../../mcp/RECOMMENDED_SERVERS.md (cloud/GitHub tools) when deploying.
Context Loading Guidance
- Requires: review/test status, version/changelog state, deploy target, approval.
- Does not require: full source, unrelated references, planning skills' bodies.
- May load:
git-workflow,github-repository, or cloud tool rules for the deploy. - Stop when: the release is done and recorded, or blocked at Gate 7.
Token Efficiency Guidance
Work from gate/status summaries, not raw source. Keep the release record to criteria met, actions taken, and outcome.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most plan spec skills give in 783 tokens
Counted across 1,099 of the 1,860 authors here whose files we hold, read 2026-08-07
- Ask one question at a timein 51 of 1099
- Break plans into vertical slicesin 29 of 1099, across 11 files
- Publish issues in dependency orderin 27 of 1099, across 9 files
- Iterate until user approves the breakdownin 25 of 1099, across 7 files
- Explore the repository to understand the codebase statein 24 of 1099, across 7 files
- Use domain glossary vocabularyin 23 of 1099, across 5 files
- Apply correct triage labels to published issuesin 23 of 1099, across 5 files
- Prefer AFK slices over HITLin 22 of 1099, across 7 files
- Write a specification before writing any codein 22 of 1099, across 14 files
- Write failing tests before implementation codein 22 of 1099, across 20 files
- Ask clarifying questions until requirements are concretein 21 of 1099, across 13 files
- Respect existing architecture decision recordsin 20 of 1099, across 5 files
Said here and by no other author read
- confirm Gates 5 through 6 passed
- verify docs, changelog, and version are updated
- confirm git state is merged or tagged
- confirm explicit approval for publish or deploy
- ensure risky changes have a rollback path
- update changelog and version before tagging
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.