release

Validate completed milestones, obtain approval, and create a Git release tag.

8|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/ddobrin/plan-skills --skill release-ddobrin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ddobrin/plan-skills/tree/main/plugins/orchestrator/skills/release
Command: npx skills add https://github.com/ddobrin/plan-skills --skill release-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incomplete or unauthorized releases by verifying milestone completion, requiring explicit human approval, and coordinating final tagging and shipment.

Core Features & Use Cases

  • Release Readiness Verification: Confirms every milestone in the active roadmap release is marked COMPLETED and committed.
  • Approval-Gated Tagging: Requires explicit user approval before creating an annotated Git release tag or pushing tags remotely.
  • Release Handoff: Coordinates marking the release as Shipped and activating the next release in the roadmap.
  • Use Case: When all milestones for a version are complete, use this Skill to validate the roadmap, obtain approval, create the release tag, and finalize the shipment workflow.

Quick Start

Ask the release skill to verify the active release and prepare it for tagging and shipment.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify milestone completion before creating a Git release tag?

You verify release readiness by checking that all milestones in the active roadmap release are marked COMPLETED and committed before proceeding to the tagging phase.

What is the process for obtaining deployment approval before pushing Git tags?

Deployment approval requires explicit user confirmation before creating an annotated Git release tag, plus an optional confirmation step before pushing tags to a remote repository.

How do I finalize a software release shipment after all milestones are committed?

You finalize a software release shipment by validating the roadmap, obtaining explicit approval, creating the Git tag, and coordinating the product-owner handoff to mark the release as Shipped.

Can I use this release management workflow for roadmap-driven development?

Yes, this release management workflow is designed specifically for roadmap-driven development contexts where all milestones in an active release have been completed and committed.

What happens if I try to ship a release without explicit approval for the Git tagging?

Without explicit approval, the workflow halts before performing irreversible Git operations to prevent unauthorized or incomplete releases from being tagged or pushed remotely.

How does release handoff activate the next release in the roadmap?

Release handoff coordinates marking the current release as Shipped and subsequently activates the next scheduled release within the active roadmap workflow.