ce-release-task

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

Identify, implement, and verify the next release task from plan files.

78|15|Updated May 1, 2023

Search Tags:#automation #planning #testing #release-management #continuous-delivery #adrs #code-changes

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The CE release task skill automates identifying the next actionable release task from the current release plan, implements the planned changes, and verifies closure with tests and gates.

Core Features & Use Cases

End-to-end release task handling from plan review to task delivery.
Plan-driven implementation with ADR and standards consultation.
Verification via tests, gates, and status updates to the plan.

Quick Start

Identify the next actionable release task from the current plan and execute it end-to-end with verification.

Frequently Asked Questions about ce-release-task

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

FAQPage Schema

How do I automate release task implementation from a markdown plan?▼

Release task automation works by identifying the next actionable task from your markdown plan, implementing the required code changes, and verifying closure through automated tests and gating checks.

How do I execute release tasks tracked in RELEASE_PLAN_v1.md?▼

To execute release tasks tracked in RELEASE_PLAN_v1.md, the system identifies the next actionable item, implements the planned changes, and updates the plan status with verification evidence from tests and gates.

What is the best way to verify code changes meet release management standards?▼

Verifying code changes for release management standards is done by applying gating tests and checking compliance against ADR standards, ensuring all release requirements are met before status updates.

Do I need ADR standards to perform continuous delivery task planning?▼

ADR standards are required for continuous delivery task planning to ensure planned code changes align with architectural decisions and pass the necessary gating tests for release verification.

Can I use this approach for end-to-end continuous delivery from plan to deployment?▼

Yes, this approach supports end-to-end continuous delivery by handling the full release task lifecycle from plan review and implementation to test execution and final status updates with evidence.