wf-release

Enforce a structured release checklist with verification and rollback planning.

5|Updated Oct 22, 2025

Search Tags:#workflow #changelog #deployment #verification #release #shipping

Ready to run

npx skills add https://github.com/marchatton/agent-skills --skill wf-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wf-release
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/06-release/wf-release
Command: npx skills add https://github.com/marchatton/agent-skills --skill wf-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines the process of releasing software changes by ensuring a checklist is followed, verification is performed, and a clean handoff occurs, minimizing risks and improving release quality.

Core Features & Use Cases

Guided Release Process: Ensures essential steps like verification and release note generation are not missed.
Risk Mitigation: Mandates pre-release verification and clear rollback plans.
Use Case: A development team needs to deploy a new feature. This skill guides them through confirming the scope, running automated tests, drafting release notes, and planning post-release monitoring.

Quick Start

Use the wf-release skill to prepare for shipping the current changes.

Frequently Asked Questions about wf-release

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

FAQPage Schema

What is a GO/NO-GO decision in a software release workflow?▼

A GO/NO-GO decision in a release workflow is a checkpoint that determines deployment readiness based on verification evidence and rollback planning to minimize shipping risks.

How do I generate a changelog and plan rollback procedures for shipping changes?▼

Generate a changelog and plan rollback procedures by following a guided release process that automates release note drafting and mandates clear recovery plans before deployment.

Can I use prd.json and plan.md files to define deployment scope and rollout details?▼

Yes, you can use prd.json to define release scope and plan.md to specify rollout details, ensuring the deployment verification process aligns with your planned changes.

What are the limitations of a checklist-based release process for software shipping?▼

A checklist-based release process relies on accurate scope confirmation and pre-release verification evidence, meaning it cannot prevent failures if the input deployment plan or automated tests are flawed.