agentic-engineering-release

Executes controlled, reversible product releases with verified rollback and staged rollout.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-release-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentic-engineering-release
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/skills/agentic-engineering-release
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-release-dagimalemayehuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a release without explicit approval gates, verified rollback paths, or observable rollout state leads to failed launches that are hard to detect and recover from. This Skill enforces a controlled release process with authority checks, rollback verification, and a complete release record. ## Core Features & Use Cases - Controlled Release Execution: Requires explicit launch authority before proceeding and stops immediately if rollback cannot be verified. - Progressive Rollout: Prefers staged exposure with feature flags, migration ordering, and post-deployment smoke verification. - Versioned Release Record: Produces a record containing approvals, artifacts, change log, deployment and migration evidence, rollout state, rollback status, and operational handoff. - Use Case: After independent assurance passes on a release candidate, use this Skill to coordinate versioning, staged deployment behind feature flags, smoke checks, and a documented handoff to operations. ## Quick Start Use $agentic-engineering-release to prepare and execute a controlled release of the approved candidate with verified rollback.

Frequently Asked Questions about agentic-engineering-release

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

FAQPage Schema
How do I execute a controlled software release with rollback?▼

Invoke the release phase after independent assurance passes. It requires explicit launch authority, verifies rollback before any rollout, prefers progressive exposure, and records deployment evidence, rollout state, and rollback status in a versioned release record.

What does the release record produced by this skill contain?▼

The versioned release record includes approvals, artifacts, change log, deployment and migration evidence, rollout state, post-deployment check results, rollback status, and the operational handoff for the team taking over.

When should I use the release phase versus the main agentic-engineering skill?▼

Use the release phase only when its boundary is known, meaning independent assurance is complete and you need versioning, rollout, or launch execution. Otherwise start with the main agentic-engineering skill, which routes to the correct phase.

What happens if rollback cannot be verified before deployment?▼

The skill stops without proceeding. It requires verified rollback readiness and explicit release authority before rollout, and it never hides a failed launch, halting at the operations boundary instead.

Does this skill handle feature flags and staged rollouts?▼

Yes. The release phase covers feature flags, staged rollout, and migration ordering, preferring progressive exposure over big-bang deployment and verifying each stage with post-deployment smoke checks.