Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/team-release
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.
Passed 22 of 23 test cases with the skill, and 4 of 23 without it.
and 26 more in the full report
18 fixed4 passed either way1 still failing0 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
In `fast-track` `v4.0.0`, the configuration is set to `automation: autonomous`. Phase 5 completed with a GO verdict. The automated runner wants to immediately execute git tagging and production push without interrupting the user. Is this permitted?
| Checked | Without skill | With skill |
|---|---|---|
| Prompts the user for explicit approval before executing tagging or deployment. | Missed | Passed |
| Offers specific choices for full deployment, staging only, or stopping the release. | Missed | Passed |
The instructions your model reads when the skill loads.
Argument check: If no version number is provided:
production/session-state/active.md and the most recent file in production/milestones/ (if they exist) to infer the target version.AskUserQuestion: "Releasing [version]. Is this correct?"AskUserQuestion to ask "What version number should be released? (e.g., v1.0.0)" and wait for user input before proceeding. Do NOT default to a hardcoded version string.When this skill is invoked, orchestrate the release team through a structured pipeline.
Decision Points: At each phase transition, use AskUserQuestion to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
In collaborative mode, the user must approve before moving to the next phase.
In guided mode the pipeline advances automatically unless a phase is BLOCKED;
in autonomous mode it runs end to end, recording each phase outcome via
log_decision. Decisions in automation_always_ask categories
(is_always_ask_category helper) always prompt regardless of mode. See
.claude/docs/automation-modes.md.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,team.size,workflow,project.stage
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
Stage check — before anything is spawned. This skill ships a release, and
/gate-check release is the readiness gate that must pass first; only its PASS
sets project.stage to Release. If the resolved project.stage is anything
else — Polish, an earlier stage, or not set — stop before Phase 1 and spawn
nothing:
"The release readiness gate has not passed (project.stage: [stage]) — run
/gate-check releasefirst."
Then ask with AskUserQuestion, in every automation mode — an override is never
taken on the user's behalf: [A] Stop — I'll run /gate-check release (recommended)
/ [B] Proceed anyway — override the stage check. On [A], end the run: Verdict
BLOCKED — release gate not passed. On [B], ask (plain text) why, then record
the override as `Stage override: project.stage was [stage] — release gate not
test cases passed, vs 4 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.