Expert in analyzing and recommending release strategies for software projects. Detects existing release patterns in brownfield projects (git tags, CI/CD workflows, changelogs, version files). Suggests optimal strategies based on architecture (single-repo, multi-repo, monorepo, microservices), team size, deployment frequency, and dependencies. Creates comprehensive release-strategy.md in living docs (.specweave/docs/internal/delivery/ or projects/{id}/delivery/). Activates for release strategy, versioning strategy, multi-repo releases, monorepo versioning, semantic versioning, coordinated releases, independent releases, release planning, version alignment, brownfield release analysis, deployment strategy, CI/CD release, how to version, release best practices.
View on GitHubJanuary 25, 2026
Select agents to install to:
npx add-skill https://github.com/anton-abyzov/specweave/blob/main/plugins/specweave-release/skills/release-strategy-advisor/SKILL.md -a claude-code --skill release-strategy-advisorInstallation paths:
.claude/skills/release-strategy-advisor/# Release Strategy Advisor **Expertise**: Release management strategy design, version alignment, brownfield release pattern detection, and living documentation of delivery processes. ## Core Capabilities ### 1. Brownfield Strategy Detection **Analyzes existing projects to detect release patterns**: **Git Analysis**: - Version tags (v1.0.0, v2.1.0-rc.1, etc.) - Tag patterns (semantic versioning, date-based, custom) - Release branches (release/*, hotfix/*) - Tag frequency and cadence **CI/CD Detection**: - GitHub Actions workflows (`.github/workflows/release.yml`) - GitLab CI (`.gitlab-ci.yml`) - Jenkins pipelines (`Jenkinsfile`) - CircleCI config (`.circleci/config.yml`) - Azure Pipelines (`azure-pipelines.yml`) **Package Managers**: - NPM: `package.json` (version, scripts: version/publish) - Python: `setup.py`, `pyproject.toml` - Java: `pom.xml`, `build.gradle` - Go: `go.mod` - Ruby: `*.gemspec` - Rust: `Cargo.toml` **Monorepo Tools**: - Lerna (`lerna.json`) - Nx (`nx.json`, `workspace.json`) - Turborepo (`turbo.json`) - Yarn Workspaces (`package.json` workspaces) - Changesets (`.changeset/config.json`) **Release Automation**: - Semantic Release (`.releaserc`, `release.config.js`) - Standard Version (`.versionrc`) - Conventional Changelog - Custom release scripts ### 2. Strategy Recommendation **Suggests optimal strategy based on**: **Project Architecture**: - Single repository → Simple semver strategy - Multi-repo (2-5 repos) → Coordinated or independent - Multi-repo (5+ repos) → Umbrella versioning - Monorepo → Workspace-based versioning - Microservices → Service-level versioning **Team Factors**: - Small team (1-5) → Simple manual releases - Medium team (5-20) → Semi-automated releases - Large team (20+) → Fully automated releases **Deployment Patterns**: - Low frequency (<1/month) → Manual releases - Medium frequency (1-4/month) → Semi-automated - High frequency (daily/weekly) → Automated CI/CD - Continuous deployment → Trunk-based + feature flags