specweave 0.33.5 → 0.34.0

package/plugins/specweave-release/README.md

@@ -34,13 +34,13 @@ The **specweave-release** plugin provides end-to-end release management capabili
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-release:init` | Initialize or analyze release strategy |
-| `/specweave-release:align` | Align versions across repositories |
-| `/specweave-release:rc` | Manage release candidates |
-| `/specweave-release:coordinate` | Plan coordinated multi-repo releases |
-| `/specweave-release:publish` | Execute releases (single or multi-repo) |
-| `/specweave-release:rollback` | Rollback failed releases |
-| `/specweave-release:matrix` | Show/update version matrix |
+| `/sw-release:init` | Initialize or analyze release strategy |
+| `/sw-release:align` | Align versions across repositories |
+| `/sw-release:rc` | Manage release candidates |
+| `/sw-release:coordinate` | Plan coordinated multi-repo releases |
+| `/sw-release:publish` | Execute releases (single or multi-repo) |
+| `/sw-release:rollback` | Rollback failed releases |
+| `/sw-release:matrix` | Show/update version matrix |
 
 ## Installation
 
@@ -61,7 +61,7 @@ npx specweave init .
 
 ```bash
 # 1. Initialize release strategy
-/specweave-release:init
+/sw-release:init
 
 # Answer questions:
 # - How many repositories? [3]
@@ -73,23 +73,23 @@ npx specweave init .
 # → Recommends: Umbrella versioning strategy
 
 # 2. Create first release
-/specweave:increment "0001-v1-0-0-release"
+/sw:increment "0001-v1-0-0-release"
 
 # 3. Align versions
-/specweave-release:align
+/sw-release:align
 
 # 4. Create RC
-/specweave-release:rc create 1.0.0
+/sw-release:rc create 1.0.0
 
 # 5. Test and promote
-/specweave-release:rc promote 1.0.0-rc.3
+/sw-release:rc promote 1.0.0-rc.3
 ```
 
 ### Brownfield Project (Existing Release Process)
 
 ```bash
 # 1. Analyze existing release patterns
-/specweave-release:init
+/sw-release:init
 
 # → Detects:
 #   - Git tags (v1.0.0, v1.1.0, ...)
@@ -101,9 +101,9 @@ npx specweave init .
 # → Documents: Existing process + recommendations
 
 # 2. Start using SpecWeave for next release
-/specweave:increment "0010-v2-0-0-release"
-/specweave-release:align
-/specweave-release:rc create 2.0.0
+/sw:increment "0010-v2-0-0-release"
+/sw-release:align
+/sw-release:rc create 2.0.0
 ```
 
 ## Use Cases
@@ -117,24 +117,24 @@ npx specweave init .
 # Goal: Release v2.0.0 (breaking changes)
 
 # 1. Initialize strategy (if not done)
-/specweave-release:init
+/sw-release:init
 
 # 2. Create release increment
-/specweave:increment "0050-v2-release"
+/sw:increment "0050-v2-release"
 
 # 3. Align version (analyze commits → suggest v2.0.0)
-/specweave-release:align
+/sw-release:align
 
 # 4. Create RC
-/specweave-release:rc create 2.0.0
+/sw-release:rc create 2.0.0
 # → v2.0.0-rc.1 → staging → testing
 
 # 5. Iterate if needed
-# Fix bugs → /specweave-release:rc iterate 2.0.0-rc.1
+# Fix bugs → /sw-release:rc iterate 2.0.0-rc.1
 # → v2.0.0-rc.2
 
 # 6. Promote to production
-/specweave-release:rc promote 2.0.0-rc.3
+/sw-release:rc promote 2.0.0-rc.3
 # → v2.0.0 → gradual rollout
 ```
 
@@ -153,10 +153,10 @@ npx specweave init .
 # Goal: Product v5.0.0 (breaking changes in 3 services)
 
 # 1. Create product release increment
-/specweave:increment "0060-product-v5-release"
+/sw:increment "0060-product-v5-release"
 
 # 2. Analyze and align versions
-/specweave-release:align
+/sw-release:align
 # → Suggests:
 #   frontend: v5.0.0 (breaking)
 #   backend: v2.9.0 (feature)
@@ -165,7 +165,7 @@ npx specweave init .
 #   shared-lib: v2.0.0 (breaking)
 
 # 3. Create coordinated RC
-/specweave-release:rc create-multi product-v5.0.0
+/sw-release:rc create-multi product-v5.0.0
 # → Tags all repos with rc.1
 
 # 4. Test cross-service
@@ -173,7 +173,7 @@ npx specweave init .
 # → E2E tests (cross-service flows)
 
 # 5. Promote when ready
-/specweave-release:rc promote-multi product-v5.0.0-rc.2
+/sw-release:rc promote-multi product-v5.0.0-rc.2
 # → Wave-by-wave deployment
 # → Updates version matrix
 ```
@@ -186,12 +186,12 @@ npx specweave init .
 # Current: 12 packages with different versions
 
 # 1. Initialize strategy (detects Lerna)
-/specweave-release:init
+/sw-release:init
 # → Detects: Lerna independent mode
 # → Documents: Current approach
 
 # 2. Align versions (only changed packages)
-/specweave-release:align
+/sw-release:align
 # → Analyzes commits per package
 # → Suggests bumps for changed packages only
 # → Validates inter-package dependencies
@@ -413,7 +413,7 @@ Recommendations:
 
 ```bash
 # Tag all repos with same RC iteration
-/specweave-release:rc create-multi product-v3.0.0
+/sw-release:rc create-multi product-v3.0.0
 
 # Creates:
 # - frontend: v5.0.0-rc.1
@@ -425,7 +425,7 @@ Recommendations:
 # Run E2E tests
 
 # Found bugs → iterate
-/specweave-release:rc iterate-multi product-v3.0.0-rc.1
+/sw-release:rc iterate-multi product-v3.0.0-rc.1
 
 # Creates:
 # - frontend: v5.0.0-rc.2 (bug fixed)
@@ -433,7 +433,7 @@ Recommendations:
 # - backend: v3.0.0-rc.1 (unchanged)
 
 # All pass → promote
-/specweave-release:rc promote-multi product-v3.0.0-rc.2
+/sw-release:rc promote-multi product-v3.0.0-rc.2
 ```
 
 ### Hotfix Workflow
@@ -471,13 +471,13 @@ git merge hotfix/v2.0.1
 **Issue**: RC testing failed
 ```bash
 # Solution: Fix issues, iterate to next RC
-/specweave-release:rc iterate 1.0.0-rc.1
+/sw-release:rc iterate 1.0.0-rc.1
 ```
 
 **Issue**: Canary deployment showing errors
 ```bash
 # Solution: Rollback immediately
-/specweave-release:rc rollback 1.0.0-rc.3
+/sw-release:rc rollback 1.0.0-rc.3
 ```
 
 ## Examples

package/plugins/specweave-release/agents/release-manager/AGENT.md

@@ -293,7 +293,7 @@ Release Manager:
      - Promote to v2.0.0 when all tests pass
 
   5. Create release increment
-     /specweave:increment "0055-backend-v2-release"
+     /sw:increment "0055-backend-v2-release"
      Generates: spec.md, plan.md, tasks.md
 
   6. Execute release (if user confirms)
@@ -341,7 +341,7 @@ Release Manager:
      frontend: v4.2.0 → v5.0.0 (breaking: React 18)
 
   5. Create coordinated release plan
-     /specweave:increment "0060-product-v4-release"
+     /sw:increment "0060-product-v4-release"
 
      spec.md:
        - Product v4.0.0 umbrella
@@ -429,18 +429,18 @@ Release Manager:
 # I work seamlessly with SpecWeave's increment workflow
 
 1. Planning Phase
-   /specweave:increment "0065-product-v5-release"
+   /sw:increment "0065-product-v5-release"
    → I'm automatically invoked to create release plan
    → Generate spec.md, plan.md, tasks.md
 
 2. Execution Phase
-   /specweave:do
+   /sw:do
    → I orchestrate wave-by-wave execution
    → Validate at each gate
    → Update task completion
 
 3. Completion Phase
-   /specweave:done 0065
+   /sw:done 0065
    → I validate all releases successful
    → Update living docs
    → Sync to external tools (GitHub, Jira)
@@ -482,18 +482,18 @@ I receive detection results:
 ## Commands I Support
 
 **Primary Commands**:
-- `/specweave-release:init` - Initialize or analyze release strategy
-- `/specweave-release:align` - Align versions across repos
-- `/specweave-release:rc` - Create/manage release candidates
-- `/specweave-release:coordinate` - Plan coordinated multi-repo release
-- `/specweave-release:publish` - Execute release (single or multi-repo)
-- `/specweave-release:rollback` - Rollback failed release
-- `/specweave-release:matrix` - Show/update version matrix
+- `/sw-release:init` - Initialize or analyze release strategy
+- `/sw-release:align` - Align versions across repos
+- `/sw-release:rc` - Create/manage release candidates
+- `/sw-release:coordinate` - Plan coordinated multi-repo release
+- `/sw-release:publish` - Execute release (single or multi-repo)
+- `/sw-release:rollback` - Rollback failed release
+- `/sw-release:matrix` - Show/update version matrix
 
 **Status Commands**:
-- `/specweave-release:status` - Show release status
-- `/specweave-release:rc-status` - Show RC testing status
-- `/specweave-release:validate` - Run pre-release validation
+- `/sw-release:status` - Show release status
+- `/sw-release:rc-status` - Show RC testing status
+- `/sw-release:validate` - Run pre-release validation
 
 ## When to Invoke Me
 
@@ -588,7 +588,7 @@ Would you like me to proceed with these steps?
 ### Example 2: Multi-Repo Release Execution
 
 ```
-User: "/specweave-release:coordinate product-v3"
+User: "/sw-release:coordinate product-v3"
 
 Release Manager: I'll orchestrate the Product v3.0.0 release across all repositories.
 
@@ -626,7 +626,7 @@ Would you like me to:
 ### Example 3: RC Management
 
 ```
-User: "/specweave-release:rc create 2.0.0"
+User: "/sw-release:rc create 2.0.0"
 
 Release Manager: Creating Release Candidate for v2.0.0...
 
@@ -656,7 +656,7 @@ Next steps:
 1. Wait for CI/CD to complete
 2. Deploy to staging
 3. Run validation tests
-4. Review RC status: /specweave-release:rc-status 2.0.0-rc.1
+4. Review RC status: /sw-release:rc-status 2.0.0-rc.1
 5. If issues found: Iterate to rc.2
 6. If all pass: Promote to v2.0.0
 ```

package/plugins/specweave-release/commands/{specweave-release-align.md → align.md}

@@ -1,9 +1,9 @@
 ---
-name: specweave-release:align
+name: sw-release:align
 description: Align versions across multiple repositories according to release strategy. Analyzes conventional commits to suggest version bumps, detects version conflicts, validates cross-repo compatibility, and executes version alignment (updates package.json, creates git tags, updates changelogs). Supports lockstep, independent, and umbrella versioning strategies.
 ---
 
-# /specweave-release:align - Align Repository Versions
+# /sw-release:align - Align Repository Versions
 
 Align versions across multiple repositories according to your release strategy.
 
@@ -20,21 +20,21 @@ Align versions across multiple repositories according to your release strategy.
 
 ```bash
 # Interactive alignment (prompts for confirmation)
-/specweave-release:align
+/sw-release:align
 
 # Align specific repositories only
-/specweave-release:align --repos frontend,backend
+/sw-release:align --repos frontend,backend
 
 # Dry run (show what would change, don't execute)
-/specweave-release:align --dry-run
+/sw-release:align --dry-run
 
 # Force alignment (skip validation)
-/specweave-release:align --force
+/sw-release:align --force
 
 # Align for specific strategy
-/specweave-release:align --strategy lockstep
-/specweave-release:align --strategy independent
-/specweave-release:align --strategy umbrella
+/sw-release:align --strategy lockstep
+/sw-release:align --strategy independent
+/sw-release:align --strategy umbrella
 ```
 
 ## Workflow
@@ -222,7 +222,7 @@ shared-lib (v1.5.0 → v1.5.1):
 Version alignment complete! ✓
 
 Next steps:
-1. Create release increment: /specweave:increment "0080-product-v5-release"
+1. Create release increment: /sw:increment "0080-product-v5-release"
 2. Or trigger CI/CD: Git tags will trigger automated releases
 3. Monitor: Check CI/CD pipelines for build/test/publish
 ```
@@ -394,13 +394,13 @@ test: add unit tests
 
 ```bash
 # Align versions within a specific project
-/specweave-release:align --project frontend-team
+/sw-release:align --project frontend-team
 
 # Align across all projects
-/specweave-release:align --all-projects
+/sw-release:align --all-projects
 
 # Align specific project's repos only
-/specweave-release:align --project backend-team --repos api,database
+/sw-release:align --project backend-team --repos api,database
 ```
 
 ## Best Practices
@@ -428,7 +428,7 @@ test: add unit tests
 ### Lockstep Alignment
 
 ```bash
-User: /specweave-release:align --strategy lockstep
+User: /sw-release:align --strategy lockstep
 
 Release Manager: Analyzing repositories with lockstep strategy...
 
@@ -457,7 +457,7 @@ Proposed:
 ### Independent Alignment with Conflict
 
 ```bash
-User: /specweave-release:align
+User: /sw-release:align
 
 Release Manager: Analyzing repositories with independent strategy...
 
@@ -484,10 +484,10 @@ Would you like me to create a coordinated release increment?
 
 ## Related Commands
 
-- `/specweave-release:init` - Initialize release strategy
-- `/specweave-release:rc` - Create release candidates for aligned versions
-- `/specweave-release:coordinate` - Plan coordinated multi-repo release
-- `/specweave-release:publish` - Execute release after alignment
+- `/sw-release:init` - Initialize release strategy
+- `/sw-release:rc` - Create release candidates for aligned versions
+- `/sw-release:coordinate` - Plan coordinated multi-repo release
+- `/sw-release:publish` - Execute release after alignment
 
 ## Dependencies
 

package/plugins/specweave-release/commands/{specweave-release-init.md → init.md}

@@ -1,9 +1,9 @@
 ---
-name: specweave-release:init
+name: sw-release:init
 description: Initialize or analyze release strategy for the project. For new projects, recommends optimal release approach based on architecture, team size, and deployment frequency. For brownfield projects, detects existing release patterns from git history, CI/CD configs, and package managers, then documents the strategy. Creates release-strategy.md in living docs with comprehensive release process documentation.
 ---
 
-# /specweave-release:init - Initialize Release Strategy
+# /sw-release:init - Initialize Release Strategy
 
 Initialize or analyze the release strategy for your project.
 
@@ -28,13 +28,13 @@ Initialize or analyze the release strategy for your project.
 
 ```bash
 # Interactive analysis and recommendation
-/specweave-release:init
+/sw-release:init
 
 # Force re-analysis (overwrite existing strategy)
-/specweave-release:init --force
+/sw-release:init --force
 
 # Quick analysis (no interactive prompts, use defaults)
-/specweave-release:init --quick
+/sw-release:init --quick
 ```
 
 ## Workflow
@@ -69,7 +69,7 @@ Initialize or analyze the release strategy for your project.
    → Set up CI/CD automation (GitHub Actions template provided)
    → Configure semantic-release or Changesets
    → Define release waves (dependency order)
-   → Create first release increment: /specweave:increment "0001-v1-release"
+   → Create first release increment: /sw:increment "0001-v1-release"
 ```
 
 ### Brownfield Projects
@@ -262,27 +262,27 @@ Or cross-project if all projects share the same strategy:
 
 1. **Create first release increment**:
    ```bash
-   /specweave:increment "0001-v1-0-0-release"
+   /sw:increment "0001-v1-0-0-release"
    ```
 
 2. **Align versions** (for multi-repo):
    ```bash
-   /specweave-release:align
+   /sw-release:align
    ```
 
 3. **Create RC** (for major versions):
    ```bash
-   /specweave-release:rc create 1.0.0
+   /sw-release:rc create 1.0.0
    ```
 
 4. **Execute release**:
    ```bash
-   /specweave:do
+   /sw:do
    ```
 
 5. **Complete release**:
    ```bash
-   /specweave:done 0001
+   /sw:done 0001
    ```
 
 ## Brownfield Integration
@@ -332,7 +332,7 @@ Or cross-project if all projects share the same strategy:
 ### Greenfield Project
 
 ```bash
-User: /specweave-release:init
+User: /sw-release:init
 
 Release Manager: I'll help you set up your release strategy.
 
@@ -358,7 +358,7 @@ Release Manager: I'll help you set up your release strategy.
 5. Next steps:
    - Set up GitHub Actions workflow
    - Configure semantic-release
-   - Create first release: /specweave:increment "0001-v1-0-0-release"
+   - Create first release: /sw:increment "0001-v1-0-0-release"
 
 Would you like me to create a GitHub Actions workflow template?
 ```
@@ -366,7 +366,7 @@ Would you like me to create a GitHub Actions workflow template?
 ### Brownfield Project
 
 ```bash
-User: /specweave-release:init
+User: /sw-release:init
 
 Release Manager: I'll analyze your existing release process.
 
@@ -407,11 +407,11 @@ Would you like me to create version matrix documentation?
 
 ## Related Commands
 
-- `/specweave-release:align` - Align versions across repos
-- `/specweave-release:rc` - Manage release candidates
-- `/specweave-release:coordinate` - Plan multi-repo releases
-- `/specweave-release:publish` - Execute releases
-- `/specweave:increment` - Create release increment
+- `/sw-release:align` - Align versions across repos
+- `/sw-release:rc` - Manage release candidates
+- `/sw-release:coordinate` - Plan multi-repo releases
+- `/sw-release:publish` - Execute releases
+- `/sw:increment` - Create release increment
 
 ## Dependencies
 

package/plugins/specweave-release/commands/{specweave-release-npm.md → npm.md}

@@ -1,9 +1,9 @@
 ---
-name: specweave-release:npm
+name: sw-release:npm
 description: Bump patch version, auto-commit dirty changes, push to GitHub, build, publish to npmjs.org. Use --quick for save+release (no GH workflow). Use --ci for GitHub Actions publish. Use --only for local publish without git push. Use --only --local for version bump only.
 ---
 
-# /specweave-release:npm - NPM Release Automation
+# /sw-release:npm - NPM Release Automation
 
 You are the NPM Release Assistant. Your job is to automate the patch version release process.
 
@@ -11,11 +11,11 @@ You are the NPM Release Assistant. Your job is to automate the patch version rel
 
 | Command | Flow | Use Case |
 |---------|------|----------|
-| `/specweave-release:npm` | Auto-commit → **PUSH** → Bump → Build → **Publish** → Push tag | **DEFAULT: INSTANT RELEASE** |
-| `/specweave-release:npm --quick` | Auto-commit → **PUSH** → Bump → Build → **Publish locally** → NO GH workflow | **QUICK: Save + Local Release** |
-| `/specweave-release:npm --ci` | Bump → Push → **CI publishes** | Let GitHub Actions handle npm publish |
-| `/specweave-release:npm --only` | Bump → Build → **Publish locally** → NO push | Quick local release, push later |
-| `/specweave-release:npm --only --local` | **Bump ONLY** → NO build, NO publish, NO git | FASTEST: Local testing only |
+| `/sw-release:npm` | Auto-commit → **PUSH** → Bump → Build → **Publish** → Push tag | **DEFAULT: INSTANT RELEASE** |
+| `/sw-release:npm --quick` | Auto-commit → **PUSH** → Bump → Build → **Publish locally** → NO GH workflow | **QUICK: Save + Local Release** |
+| `/sw-release:npm --ci` | Bump → Push → **CI publishes** | Let GitHub Actions handle npm publish |
+| `/sw-release:npm --only` | Bump → Build → **Publish locally** → NO push | Quick local release, push later |
+| `/sw-release:npm --only --local` | **Bump ONLY** → NO build, NO publish, NO git | FASTEST: Local testing only |
 
 ## Detecting Mode
 
@@ -166,7 +166,7 @@ git push origin develop --follow-tags
 
 ## QUICK MODE WORKFLOW (--quick flag) - SAVE + LOCAL RELEASE
 
-Use this workflow when `--quick` flag is detected. This combines `/specweave:save` behavior with local npm publish. **NO GitHub workflow trigger** - everything happens locally.
+Use this workflow when `--quick` flag is detected. This combines `/sw:save` behavior with local npm publish. **NO GitHub workflow trigger** - everything happens locally.
 
 **Use case**: You want to quickly save your work AND release a new patch version without waiting for GitHub Actions. Perfect for:
 - Hotfixes that need immediate npm availability
@@ -460,19 +460,19 @@ Show the user:
 
 ```bash
 # DEFAULT: Instant release (auto-commits dirty, publishes, pushes + tag)
-/specweave-release:npm
+/sw-release:npm
 
 # QUICK: Save + local release (auto-commits, pushes, publishes - NO GH workflow)
-/specweave-release:npm --quick
+/sw-release:npm --quick
 
 # CI release (GitHub Actions handles npm publish) - requires clean tree
-/specweave-release:npm --ci
+/sw-release:npm --ci
 
 # Quick local publish, sync git later
-/specweave-release:npm --only
+/sw-release:npm --only
 
 # FASTEST: Version bump only (no publish, no git, no build)
-/specweave-release:npm --only --local
+/sw-release:npm --only --local
 ```
 
 | Scenario | Command | Auto-Commit Dirty? | NPM Published By | Git Pushed | Tag Pushed |
@@ -541,7 +541,7 @@ Show the user:
 5. Publish: `npm publish --registry https://registry.npmjs.org`
 6. Push: `git push origin develop --follow-tags`
 
-**Or use**: `/specweave-release:npm` (no flags) for full instant release
+**Or use**: `/sw-release:npm` (no flags) for full instant release
 ```
 
 ## Local Mode Safety Rules

package/plugins/specweave-release/commands/{specweave-release-platform.md → platform.md}

@@ -1,6 +1,6 @@
 ---
-name: specweave-release:platform
-description: "Coordinate multi-repo platform releases with synchronized versioning, RC workflow, and GitFlow integration. Usage: /specweave-release:platform create|promote|status"
+name: sw-release:platform
+description: "Coordinate multi-repo platform releases with synchronized versioning, RC workflow, and GitFlow integration. Usage: /sw-release:platform create|promote|status"
 ---
 
 # Platform Release Coordination
@@ -16,12 +16,12 @@ description: "Coordinate multi-repo platform releases with synchronized versioni
 ### Create Platform RC
 
 ```bash
-/specweave-release:platform create <platform-version>
+/sw-release:platform create <platform-version>
 ```
 
 **Example**:
 ```bash
-/specweave-release:platform create v3.0.0
+/sw-release:platform create v3.0.0
 ```
 
 **What it does**:
@@ -67,8 +67,8 @@ Step 6: Updating version matrix...
 Next steps:
 1. Deploy to staging
 2. Run E2E tests
-3. If tests pass: /specweave-release:platform promote v3.0.0-rc.1
-4. If tests fail: /specweave-release:platform iterate v3.0.0-rc.1
+3. If tests pass: /sw-release:platform promote v3.0.0-rc.1
+4. If tests fail: /sw-release:platform iterate v3.0.0-rc.1
 ```
 
 ---
@@ -76,12 +76,12 @@ Next steps:
 ### Iterate Platform RC
 
 ```bash
-/specweave-release:platform iterate <platform-rc-version>
+/sw-release:platform iterate <platform-rc-version>
 ```
 
 **Example**:
 ```bash
-/specweave-release:platform iterate v3.0.0-rc.1
+/sw-release:platform iterate v3.0.0-rc.1
 ```
 
 **What it does**:
@@ -112,12 +112,12 @@ Creating RC.2 for changed repos:
 ### Promote Platform RC to Production
 
 ```bash
-/specweave-release:platform promote <platform-rc-version>
+/sw-release:platform promote <platform-rc-version>
 ```
 
 **Example**:
 ```bash
-/specweave-release:platform promote v3.0.0-rc.3
+/sw-release:platform promote v3.0.0-rc.3
 ```
 
 **What it does**:
@@ -192,12 +192,12 @@ Deployment URLs:
 ### Platform Release Status
 
 ```bash
-/specweave-release:platform status [platform-version]
+/sw-release:platform status [platform-version]
 ```
 
 **Example**:
 ```bash
-/specweave-release:platform status v3.0.0
+/sw-release:platform status v3.0.0
 ```
 
 **Output**:
@@ -225,9 +225,9 @@ Blockers:
 
 Next Steps:
   1. Fix api-gateway auth flow
-  2. Create RC.3: /specweave-release:platform iterate v3.0.0-rc.2
+  2. Create RC.3: /sw-release:platform iterate v3.0.0-rc.2
   3. Re-test
-  4. Promote: /specweave-release:platform promote v3.0.0-rc.3
+  4. Promote: /sw-release:platform promote v3.0.0-rc.3
 ```
 
 ---
@@ -408,21 +408,21 @@ Next Steps:
 # Solution: Resolve conflicts manually, then resume
 git add .
 git commit -m "Resolved conflicts"
-/specweave-release:platform promote v3.0.0-rc.3 --resume
+/sw-release:platform promote v3.0.0-rc.3 --resume
 ```
 
 **Issue**: One service fails tests
 ```bash
 # Solution: Fix the service, create new RC
 # (Don't bump other services that passed)
-/specweave-release:platform iterate v3.0.0-rc.2
+/sw-release:platform iterate v3.0.0-rc.2
 ```
 
 **Issue**: Need to rollback
 ```bash
 # Solution: Revert main to previous tag, create hotfix
 git revert <commit>
-/specweave-release:platform create v3.0.1
+/sw-release:platform create v3.0.1
 ```
 
 ---