Library use: Apply the compatibility and execution contract. Source roles, memory claims, command names, hooks, and integrations are instructions or prerequisites—not installed capabilities.

Release

When to use

Prepare, document, land, deploy, and monitor a verified change.

Inputs

User objective, project constraints, relevant source or evidence, and explicit success criteria.

Procedure and handoffs

1. Load the verification-loop procedure. Record acceptance evidence for the candidate revision.
2. Load the ship procedure. Prepare PR/release artifacts within authorization.
3. Load the document-release procedure. Reconcile documentation with the actual shipped behavior.
4. Load the land-and-deploy procedure. If authorized, land and deploy; retain rollback and production-verification evidence.
5. Load the canary procedure. Monitor scoped health signals and report incidents or regressions.

Verification and output

Produce the artifacts required by the selected procedures and an evidence-backed status: completed, failed, skipped with reason, or blocked on a named prerequisite. Carry unresolved findings forward. Do not treat an unavailable tool, an unrun check, or a reviewer failure as a pass.

Scope and compatibility

Select stages proportionate to the task. Preserve required gates of the chosen variant; record exceptions. Read the compatibility policy before combining conflicting variants. These instructions do not grant tool access or authorize publishing, commits, deployment, or communications.

Related skills and principles

• core/goal-driven-execution
• core/simplicity-first
• core/surgical-changes
• core/think-before-coding
• release/canary
• release/document-release
• release/land-and-deploy
• release/ship
• verification/verification-loop
• workflows/dev-context

Source provenance

• ecc/skills/verification-loop/SKILL.md
• gstack/ship/SKILL.md
• gstack/document-release/SKILL.md
• gstack/land-and-deploy/SKILL.md
• gstack/canary/SKILL.md