lean-release
Installation
SKILL.md
lean-release
Ground rules
- Standalone. Standalone skill: follow the request, project instructions and actual deployment tools.
- No installation. No provider, runtime or companion is required.
- Reuse. Reuse existing acceptance, validation and authorization.
- Depth. Procedure depth defaults to standard and does not alter model settings or permissions.
Input and result
- Input. Input is the application, requested version/artifact, target environment and endpoint: plan, release or recovery. Identify the exact source revision plus pending changes or immutable artifact, destination/account/environment, current deployed state and requested outcome. Resolve ambiguous targets before mutation.
- Authorization. A plan-only request ends with a plan. An explicit release request authorizes matching work; ask again only for a genuinely missing material decision or approval required by the user, project or tool.
- READY. A complete, actionable plan is READY with exact target/artifact, steps, checks, recovery strategy and outstanding prerequisites.
- BLOCKED plan. A plan with an indispensable unresolved decision is BLOCKED with completed planning and the needed answer; unavailable execution credentials do not block a plan that does not require them.
- DONE. A release or requested rollback is DONE only when that endpoint's mandatory artifact, target, health, data and delivery conditions have current evidence.
- BLOCKED and FAILED. Missing prerequisites are BLOCKED; an executed endpoint with unresolved demonstrated failure is FAILED.
- Failed release. A failed release followed by successful rollback is FAILED for the release, with recovery separately DONE; it does not satisfy shipping the requested version.
- Report. Report requested and resulting versions/environment, commands/operation IDs, checks and outcomes, migration/recovery state, observation limits and next action. When a controller owns the larger task, return this evidence and preserve its repair budget. Keep release notes or a continuation record in an existing agreed location; do not create workflow files, commit, tag, push or publish documentation as incidental steps.