release-evidence

Assemble a bounded milestone release-evidence packet into Markdown and JSON artifacts.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill release-evidence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-evidence
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/release-evidence
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill release-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables teams to assemble a bounded milestone release-evidence packet that captures proofs, gaps, and risks, without performing release authority actions.

Core Features & Use Cases

  • Assemble a bounded release-evidence packet from milestone, issue and PR evidence, demos, reviews, remediation, and validation surfaces.
  • Classify the packet as ready, partial, blocked, or not_run to guide release-readiness discussions.
  • Provide Markdown and JSON artifacts that support handoff to gap-analysis, PR finish, or release ceremony workflows.

Quick Start

Run the deterministic helper with milestone, milestone-root, and output path to generate the release-evidence package.

Frequently Asked Questions about release-evidence

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

FAQPage Schema
How do I assemble release evidence for a milestone closeout?

A release-evidence packet captures proofs, gaps, and risks for milestone closeout by aggregating issues, PRs, demos, reviews, remediation, and validation surfaces into one bounded artifact stating what is proven, what remains open, and what is not claimed.

What is a bounded release-evidence packet used for?

A release-evidence packet captures proofs, gaps, and risks for milestone closeout by aggregating issues, PRs, demos, reviews, remediation, and validation surfaces into one bounded artifact stating what is proven, what remains open, and what is not claimed.

How do I classify release readiness using milestone evidence?

You classify release readiness by evaluating assembled milestone evidence, which automatically categorizes the release-evidence packet status as ready, partial, blocked, or not_run to guide release-readiness discussions.

What inputs do I need to generate a release-evidence package?

Generating a release-evidence package requires milestone, milestone-root, evidence, and policy inputs, which the assembly script processes to output bounded Markdown and JSON artifacts at a defined output root.

Can release-evidence packets perform release authority actions?

Release-evidence packets cannot perform release authority actions; they strictly assemble bounded evidence covering issues, PRs, demos, and validation to support handoff to gap-analysis or release ceremony workflows.

What is the best way to document non-claims and residual risks for release reviews?

The best way to document non-claims and residual risks for release reviews is assembling a bounded release-evidence packet that explicitly states what is proven, what remains open, and what is not claimed in Markdown and JSON formats.