team-release
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
Argument check: If no version number is provided:
- Read
production/session-state/active.mdand the most recent file inproduction/milestones/(if they exist) to infer the target version. - If a version is found: report "No version argument provided — inferred [version] from milestone data. Proceeding." Then confirm with
AskUserQuestion: "Releasing [version]. Is this correct?" - If no version is discoverable: use
AskUserQuestionto 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.
Phase 0: Resolve Config
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,team.size,workflow,project.stage