ce-release-check

Name: ce-release-check
Availability: InStock
Author: moffran

Identify release versions, scan gates, and propose the next actionable work item.

78|15|Updated May 1, 2023

Search Tags:#automation #planning #adr #release #governance #change-log

Ready to run

npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-release-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-release-check
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-release-check
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-release-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reads the release plan and ADR governance to determine the next development step that aligns with the plan and constraints.

Core Features & Use Cases

Identify the current released version and target milestone from RELEASE_PLAN_v1.md.
Scan open gates for the target milestone and identify governing ADRs using ce-adr-consult to surface constraints.
Propose the next actionable work item by prioritizing blocking gates, open ADR gaps, and non-gate improvements, and verify against CHANGELOG to avoid duplicates.
Ensure ADR constraints take precedence when a conflict exists, preventing unsafe roadmap commitments.

Quick Start

Run the ce-release-check to compute the next actionable release step from the current release plan.

Frequently Asked Questions about ce-release-check

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

FAQPage Schema

How do I automate release planning using ADR constraints?▼

Release planning automation identifies your target milestone from RELEASE_PLAN_v1.md, scans open gates, and surfaces governing ADR constraints to propose the next actionable work item.

How do I determine the next actionable work item for a release milestone?▼

To determine the next actionable work item, the tool prioritizes blocking gates, open ADR gaps, and non-gate improvements, verifying against CHANGELOG to avoid duplicates.

What is ADR-aware governance in release planning?▼

ADR-aware governance ensures architectural decision records take precedence when conflicts exist, preventing unsafe roadmap commitments during release planning and gate validation.

How do I avoid duplicate entries in a change log during release planning?▼

Avoid duplicate change log entries by verifying proposed actionable work items against the existing CHANGELOG before committing to the next development step.

Can I use release planning automation without a RELEASE_PLAN_v1.md file?▼

No, release planning automation requires a RELEASE_PLAN_v1.md file to identify the current released version and target next milestone for computing the next step.

Why does an ADR constraint override a non-gate improvement in release planning?▼

ADR constraints override non-gate improvements because ADR-aware governance prioritizes architectural decisions to prevent unsafe roadmap commitments during milestone gate validation.