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, and list the release-blocking
@critical scenarios with the passing test behind each (../../system/GHERKIN_RULES.md). One without a passing test blocks the release.
- 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 — on a tracked project as a
DEPLOY- task in the week, a development-log entry, and the week's report (project-management, ../../system/PROJECT_MANAGEMENT_RULES.md).
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.md for 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
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, project-management.
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.
1---2name: release-planning3description: 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.4metadata:5 source: https://skillmd.com/skills/ahtishamshahzad/release-planning6---78# Release Planning910## Purpose1112Validate 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.1314## When to Use1516- For a **release** or **deployment** request type.17- Before shipping any completed, reviewed work.18- **Not** to publish/deploy without explicit approval or a passed gate.1920## Inputs2122- The reviewed, tested change set.23- Version/changelog state; release criteria.24- Deploy target and approval status.2526## Discovery Questions2728- Are tests green and reviews complete (Gates 5–6)?29- Is the changelog/version updated?30- What is the deploy target and rollback plan?31- Has the user approved the publish/deploy step?3233## Responsibilities3435- Verify **release criteria**: tests green, security/quality review done, docs + changelog updated, version handled.36- Confirm **git workflow** followed (branch/PR/merge state).37- Plan the **release/deploy** with a rollback path.38- Ensure any **publish/deploy** step is explicitly approved.39- Record the release decision and outcome.4041## Required Workflow42431. Confirm Gates 5–6 passed, and list the release-blocking `@critical` scenarios with the passing test behind each (`../../system/GHERKIN_RULES.md`). One without a passing test blocks the release.442. Verify docs, changelog, and version are updated.453. Confirm git state (merged/tagged as required).464. Confirm explicit approval for publish/deploy.475. Execute (or hand off) the approved release with a rollback plan.486. Verify and record the outcome — on a tracked project as a `DEPLOY-` task in the week, a development-log entry, and the week's report (`project-management`, `../../system/PROJECT_MANAGEMENT_RULES.md`).4950## Decision Rules5152- Do not ship on a failed gate — stop and report.53- Publish/deploy is outward-facing → explicit approval required.54- No release without a rollback path for risky changes.55- Version/changelog updates precede tagging.5657## Rules5859- Gate 7 is mandatory; a green build alone is not release readiness.60- Follow `../../system/GIT_WORKFLOW_RULES.md` for tags/branches.61- Never expose secrets in release artifacts (`../../system/SECURITY_RULES.md`).6263## Anti-Patterns6465- Shipping with failing/absent tests.66- Deploying without approval or rollback.67- Skipping changelog/version.68- Treating a passing CI as sufficient proof of readiness.6970## Validation Checklist7172- [ ] Gates 5–6 passed.73- [ ] Docs + changelog + version updated.74- [ ] Git state correct (merged/tagged).75- [ ] Rollback plan for risky changes.76- [ ] Publish/deploy explicitly approved.77- [ ] Outcome verified and recorded.7879## Definition of Done8081Release 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.8283## Related Skills8485`git-workflow`, `github-repository`, `testing-strategy`, `security-review`, `final-quality-audit`, `migration-planning` (cutover), `project-orchestrator`, `project-management`.8687## Related Knowledge8889`../../knowledge/` (deploy targets, environments).9091## Related References9293`../../mcp/RECOMMENDED_SERVERS.md` (cloud/GitHub tools) when deploying.9495## Context Loading Guidance9697- **Requires:** review/test status, version/changelog state, deploy target, approval.98- **Does not require:** full source, unrelated references, planning skills' bodies.99- **May load:** `git-workflow`, `github-repository`, or cloud tool rules for the deploy.100- **Stop when:** the release is done and recorded, or blocked at Gate 7.101102## Token Efficiency Guidance103104Work from gate/status summaries, not raw source. Keep the release record to criteria met, actions taken, and outcome.