release-proof-pack

Generate auditable walkthrough, decision log, and release checklist artifacts for software releases.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/ricardohg1998-create/Plantilla-repo --skill release-proof-pack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-proof-pack
Source: https://github.com/ricardohg1998-create/Plantilla-repo/tree/main/.agent/skills/release-proof-pack
Command: npx skills add https://github.com/ricardohg1998-create/Plantilla-repo --skill release-proof-pack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating auditable proof artifacts for software releases.

Core Features & Use Cases

  • Walkthrough generation: guides stakeholders through the release lifecycle with traceable steps.
  • Decision log maintenance: records rationale and approvals for each gate.
  • Release checklist automation: compiles required gates and evidence into a reproducible artifact.

Quick Start

Run the Release Proof Pack workflow to produce docs/release_walkthrough.md, docs/decision_log.md, and docs/release_checklist.md.

Frequently Asked Questions about release-proof-pack

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

FAQPage Schema
How do I generate auditable release proof artifacts for software compliance?

Auditable release proof artifacts are generated by compiling a release walkthrough, decision log, and checklist. This enforces artifact creation, formatting, and distribution across the release workflow to preserve governance and compliance evidence.

What is included in a release walkthrough and decision log for governance?

A release walkthrough and decision log include traceable steps guiding stakeholders through the release lifecycle, alongside recorded rationale and approvals for each gate. These artifacts are preserved to maintain compliance.

How do I automate a release checklist for required gates and evidence?

Automating a release checklist involves compiling required gates and evidence into a reproducible artifact. This ensures all release criteria are consistently met and documented for audit purposes across the lifecycle.

Does this release proof workflow require any specific dependencies or components?

No specific dependencies or components are required to run the release proof workflow. It independently produces the necessary markdown documentation artifacts for release governance without external tool integrations.

What's the best way to maintain a decision log for software release approvals?

The best way to maintain a decision log for software release approvals is to systematically record the rationale and approvals for each gate. This creates a traceable, auditable artifact preserved throughout the release lifecycle.