specweave 0.33.5 → 0.34.0

package/plugins/specweave/skills/tdd-workflow/SKILL.md

@@ -15,8 +15,8 @@ This skill acts as a **discovery hub** for Test-Driven Development (TDD) in Spec
 
 **NOT a full TDD implementation** - delegates to:
 - `tdd-orchestrator` agent (deep TDD expertise)
-- `/specweave:tdd:cycle` command (enforced red-green-refactor)
-- Individual phase commands (`/specweave:tdd:red`, `/specweave:tdd:green`, `/specweave:tdd:refactor`)
+- `/sw:tdd:cycle` command (enforced red-green-refactor)
+- Individual phase commands (`/sw:tdd:red`, `/sw:tdd:green`, `/sw:tdd:refactor`)
 
 ---
 
@@ -64,7 +64,7 @@ Would you like to:"
 ```typescript
 Question: "How would you like to implement TDD for this feature?"
 Options:
-  1. "Guided TDD Workflow (/specweave:tdd:cycle)"
+  1. "Guided TDD Workflow (/sw:tdd:cycle)"
      Description: "Full red-green-refactor cycle with gates between phases.
                    Can't proceed to GREEN without RED test. Most rigorous."
 
@@ -81,12 +81,12 @@ Options:
 
 **Option 1: Guided TDD Workflow**
 ```bash
-Invoke: /specweave:tdd:cycle
+Invoke: /sw:tdd:cycle
 
 This command orchestrates:
-1. /specweave:tdd:red    - Write failing test (blocks until red)
-2. /specweave:tdd:green  - Implement minimal code (blocks until green)
-3. /specweave:tdd:refactor - Refactor safely (tests must stay green)
+1. /sw:tdd:red    - Write failing test (blocks until red)
+2. /sw:tdd:green  - Implement minimal code (blocks until green)
+3. /sw:tdd:refactor - Refactor safely (tests must stay green)
 
 Benefits:
 - Enforces discipline (gates prevent skipping phases)
@@ -162,7 +162,7 @@ I'll notify you at each phase transition."
 
 **In Increment Workflow**:
 ```
-/specweave:inc "Authentication feature" → spec.md created
+/sw:inc "Authentication feature" → spec.md created
 ↓
 User: "Implement with TDD"
 ↓
@@ -170,7 +170,7 @@ tdd-workflow skill activates → offers options
 ↓
 User chooses: Guided TDD Workflow
 ↓
-/specweave:tdd:cycle invoked
+/sw:tdd:cycle invoked
   ↓
   Phase 1: RED   - tests.md updated with failing tests
   Phase 2: GREEN - tasks.md implementation
@@ -193,16 +193,16 @@ tdd-workflow can coordinate test-first bug fixes
 ## Commands Reference
 
 ### Full Cycle
-- `/specweave:tdd:cycle` - Complete red-green-refactor orchestration
+- `/sw:tdd:cycle` - Complete red-green-refactor orchestration
 
 ### Individual Phases
-- `/specweave:tdd:red` - RED phase only (write failing test)
-- `/specweave:tdd:green` - GREEN phase only (make test pass)
-- `/specweave:tdd:refactor` - REFACTOR phase only (improve code)
+- `/sw:tdd:red` - RED phase only (write failing test)
+- `/sw:tdd:green` - GREEN phase only (make test pass)
+- `/sw:tdd:refactor` - REFACTOR phase only (improve code)
 
 ### When to Use Each
 
-**Use /specweave:tdd:cycle when**:
+**Use /sw:tdd:cycle when**:
 - ✅ Starting new feature from scratch
 - ✅ Learning TDD or teaching team
 - ✅ Want enforced discipline (gates)
@@ -242,7 +242,7 @@ Great! TDD (Test-Driven Development) follows red-green-refactor:
 
 **tdd-workflow**:
 ```
-Perfect! I'm invoking /specweave:tdd:cycle to orchestrate your TDD workflow.
+Perfect! I'm invoking /sw:tdd:cycle to orchestrate your TDD workflow.
 
 🔴 Starting RED phase...
 Write a failing test for user registration. Let me create the test skeleton:
@@ -252,7 +252,7 @@ Write a failing test for user registration. Let me create the test skeleton:
 ✅ Test written and failing. Run: npm test
 ❌ Expected failure confirmed.
 
-Ready to proceed to GREEN phase? (type 'yes' or run /specweave:tdd:green)
+Ready to proceed to GREEN phase? (type 'yes' or run /sw:tdd:green)
 ```
 
 ---
@@ -292,7 +292,7 @@ Invoking tdd-orchestrator agent for advanced refactoring support...
 Great! Tests are passing. Time for REFACTOR phase.
 
 You can:
-1. Run /specweave:tdd:refactor (guided refactoring)
+1. Run /sw:tdd:refactor (guided refactoring)
 2. Refactor manually (I'll verify tests stay green)
 
 Which would you prefer?
@@ -309,7 +309,7 @@ Perfect! I'll monitor your refactoring:
 ✅ Tests still passing after refactor
 ✅ TDD cycle maintained
 
-Ready for next feature? Run /specweave:tdd:cycle or continue manually.
+Ready for next feature? Run /sw:tdd:cycle or continue manually.
 ```
 
 ---
@@ -352,8 +352,8 @@ tdd:
 - `qa-lead` - Test strategy overlaps with TDD principles
 
 **Commands**:
-- `/specweave:tdd:cycle` - Full red-green-refactor orchestration
-- `/specweave:tdd:red`, `/specweave:tdd:green`, `/specweave:tdd:refactor` - Individual phases
+- `/sw:tdd:cycle` - Full red-green-refactor orchestration
+- `/sw:tdd:red`, `/sw:tdd:green`, `/sw:tdd:refactor` - Individual phases
 
 ---
 
@@ -369,7 +369,7 @@ tdd:
 
 **Not a replacement for**:
 - `tdd-orchestrator` agent (deep expertise)
-- `/specweave:tdd-*` commands (workflow enforcement)
+- `/sw:tdd-*` commands (workflow enforcement)
 
 **Instead, it's the entry point** that helps users choose the right TDD tool for their context.
 

package/plugins/specweave/skills/translator/SKILL.md

@@ -112,7 +112,7 @@ Me: *Translates spec.md, preserves framework terms, maintains formatting*
 
 ### ⏸️ **Keep in English**:
 - Framework terms: "increment", "spec.md", "plan.md", "tasks.md", "COMPLETION-SUMMARY.md"
-- SpecWeave commands: "/specweave:inc", "/specweave:do", "/specweave:progress"
+- SpecWeave commands: "/sw:inc", "/sw:do", "/sw:progress"
 - Technical terms: "TypeScript", "npm", "git", "API", "CLI"
 - File names and paths: `.specweave/`, `src/`, `CLAUDE.md`
 - Code blocks and examples
@@ -126,11 +126,11 @@ Me: *Translates spec.md, preserves framework terms, maintains formatting*
 
 ### CLI Message (English → Russian)
 
-**English**: "✅ Increment created successfully! Next: Run /specweave:do to start implementation."
+**English**: "✅ Increment created successfully! Next: Run /sw:do to start implementation."
 
-**Russian**: "✅ Increment успешно создан! Далее: Запустите /specweave:do для начала реализации."
+**Russian**: "✅ Increment успешно создан! Далее: Запустите /sw:do для начала реализации."
 
-**Note**: "Increment" kept in English (framework term), "/specweave:do" kept as-is (command)
+**Note**: "Increment" kept in English (framework term), "/sw:do" kept as-is (command)
 
 ### Documentation (English → Spanish)
 

package/plugins/specweave/skills/umbrella-repo-detector/SKILL.md

@@ -257,17 +257,17 @@ Which would you like to do?
 
 ## Saving Changes Across Repos
 
-Use `/specweave:save` to commit and push changes across all repos at once:
+Use `/sw:save` to commit and push changes across all repos at once:
 
 ```bash
 # Save all repos with same commit message
-/specweave:save "feat: Add user authentication"
+/sw:save "feat: Add user authentication"
 
 # Preview what would happen
-/specweave:save --dry-run
+/sw:save --dry-run
 
 # Save specific repos only
-/specweave:save "fix: Bug fixes" --repos frontend,backend
+/sw:save "fix: Bug fixes" --repos frontend,backend
 ```
 
 **Features:**
@@ -283,4 +283,4 @@ Use `/specweave:save` to commit and push changes across all repos at once:
 2. **Parent repo is optional** - Can have umbrella config or just independent repos
 3. **User stories MUST have project prefix** - Never generate generic `US-001` in multi-repo mode
 4. **Cross-project stories get special handling** - Tagged and linked across repos
-5. **Use `/specweave:save`** - Single command to save changes across all repos
+5. **Use `/sw:save`** - Single command to save changes across all repos

package/plugins/specweave-ado/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-ado",
+  "name": "sw-ado",
   "version": "0.24.0",
   "description": "Azure DevOps integration for SpecWeave - sync increments with ADO work items, track progress, and manage project workflows",
   "author": {

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

@@ -217,7 +217,7 @@ This ensures each increment syncs to its designated ADO project, not a global se
 
 ### 1. Work Item Creation
 
-**When**: User runs `/specweave-ado:create-workitem` or increment created with auto-sync enabled
+**When**: User runs `/sw-ado:create-workitem` or increment created with auto-sync enabled
 
 **Pre-flight checks**:
 1. **Permission**: Verify `canUpdateExternalItems = true`
@@ -262,7 +262,7 @@ POST https://dev.azure.com/{organization}/{project}/_apis/wit/workitems/${type}?
 
 ### 2. Progress Synchronization
 
-**When**: Task completes (post-task-completion hook) or manual `/specweave-ado:sync`
+**When**: Task completes (post-task-completion hook) or manual `/sw-ado:sync`
 
 **Pre-flight checks**:
 1. **Permission**: Verify `canUpdateExternalItems = true` for push operations
@@ -306,7 +306,7 @@ POST https://dev.azure.com/{organization}/{project}/_apis/wit/workitems/{id}/com
 
 ### 3. Work Item Closure
 
-**When**: Increment completes (`/specweave:done`) or manual `/specweave-ado:close-workitem`
+**When**: Increment completes (`/sw:done`) or manual `/sw-ado:close-workitem`
 
 **Pre-flight checks**:
 1. **Permission**: Verify `canUpdateExternalItems = true` AND `canUpdateStatus = true`
@@ -339,7 +339,7 @@ PATCH https://dev.azure.com/{organization}/{project}/_apis/wit/workitems/{id}?ap
 
 ### 4. Status Checking
 
-**When**: User runs `/specweave-ado:status`
+**When**: User runs `/sw-ado:status`
 
 **Actions**:
 1. Read increment metadata

package/plugins/specweave-ado/agents/ado-sync-judge/AGENT.md

@@ -61,7 +61,7 @@ if (localStatus !== externalStatus) {
    - MUST be 100% complete to close
    - All tasks completed
    - All tests passing
-   - `/specweave:done` validates strictly
+   - `/sw:done` validates strictly
    - Can be deleted after completion
 
 2. **Spec Lifecycle** (Flexible):
@@ -78,7 +78,7 @@ Verify hooks fire correctly:
 
 ```bash
 # Check 1: Post-increment completion
-Event: /specweave:done completes
+Event: /sw:done completes
 Expected: Living docs updated → Sync triggered
 Validate:
   - Hook fires within 5 seconds
@@ -230,7 +230,7 @@ fi
 # Step 3: Test increment strictness
 echo "3. Testing increment completion strictness..."
 # Try to close incomplete increment (should fail)
-RESULT=$(/specweave:done test-increment-incomplete 2>&1)
+RESULT=$(/sw:done test-increment-incomplete 2>&1)
 if [[ $RESULT != *"Cannot close increment"* ]]; then
   echo "❌ Incomplete increment was allowed to close"
   exit 1
@@ -296,7 +296,7 @@ Timeline:
   Day 3:
     - All tasks complete
     - Tests passing
-    - /specweave:done executed
+    - /sw:done executed
     - Increment: closed ✅
     - Spec synced to ADO
     - ADO status: Active

package/plugins/specweave-ado/commands/cleanup-duplicates.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado:cleanup-duplicates
+name: sw-ado:cleanup-duplicates
 description: Clean up duplicate Azure DevOps work items for a Feature. Finds work items with duplicate titles and closes all except the first created item.
 justification: |
   CRITICAL INCIDENT RESPONSE TOOL - DO NOT DELETE!
@@ -28,7 +28,7 @@ justification: |
 ## Usage
 
 ```bash
-/specweave-ado:cleanup-duplicates <feature-id> [--dry-run]
+/sw-ado:cleanup-duplicates <feature-id> [--dry-run]
 ```
 
 ## What It Does
@@ -47,7 +47,7 @@ justification: |
 ### Dry Run (No Changes)
 
 ```bash
-/specweave-ado:cleanup-duplicates FS-031 --dry-run
+/sw-ado:cleanup-duplicates FS-031 --dry-run
 ```
 
 **Output**:
@@ -79,7 +79,7 @@ This was a DRY RUN - no changes made.
 ### Actual Cleanup
 
 ```bash
-/specweave-ado:cleanup-duplicates FS-031
+/sw-ado:cleanup-duplicates FS-031
 ```
 
 **Output**:
@@ -156,7 +156,7 @@ Auto-closed by SpecWeave Duplicate Cleanup
 ```
 WARNING: 10 duplicate(s) detected!
    Run cleanup command to resolve:
-   /specweave-ado:cleanup-duplicates FS-031
+   /sw-ado:cleanup-duplicates FS-031
 ```
 
 ## Architecture
@@ -175,9 +175,9 @@ WARNING: 10 duplicate(s) detected!
 
 ## Related Commands
 
-- `/specweave-ado:sync` - Sync Feature to ADO (with duplicate detection)
-- `/specweave-ado:reconcile` - Reconcile work item states
-- `/specweave:validate` - Validate increment completeness
+- `/sw-ado:sync` - Sync Feature to ADO (with duplicate detection)
+- `/sw-ado:reconcile` - Reconcile work item states
+- `/sw:validate` - Validate increment completeness
 
 ## Implementation
 
@@ -204,7 +204,7 @@ After cleanup:
 
 1. **Verify cleanup**: Check ADO for remaining work items
 2. **Check Feature FEATURE.md**: Verify frontmatter has correct work item IDs
-3. **Re-run sync**: `/specweave-ado:sync` (should show no duplicates)
+3. **Re-run sync**: `/sw-ado:sync` (should show no duplicates)
 4. **Duplicate detection**: Automatically enabled via AdoDuplicateDetector
 
 ---

package/plugins/specweave-ado/commands/clone.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado:clone-repos
+name: sw-ado:clone-repos
 description: Clone Azure DevOps repositories to local workspace. Use after init if cloning was skipped, or to add repos later.
 ---
 
@@ -19,19 +19,19 @@ This command clones Azure DevOps repositories **after** initial SpecWeave setup
 
 ```bash
 # Interactive mode (prompts for everything)
-/specweave-ado:clone-repos
+/sw-ado:clone-repos
 
 # With pattern filter
-/specweave-ado:clone-repos --pattern "sw-*"
+/sw-ado:clone-repos --pattern "sw-*"
 
 # Regex pattern
-/specweave-ado:clone-repos --pattern "regex:^api-.*$"
+/sw-ado:clone-repos --pattern "regex:^api-.*$"
 
 # Specific project only
-/specweave-ado:clone-repos --project "MyProject"
+/sw-ado:clone-repos --project "MyProject"
 
 # Dry-run (preview only)
-/specweave-ado:clone-repos --dry-run
+/sw-ado:clone-repos --dry-run
 ```
 
 ## Your Task
@@ -265,7 +265,7 @@ await triggerAdoRepoCloning(projectPath, adoProjectSelection, clonePatternResult
 ## Examples
 
 ### Example 1: Interactive Clone
-**User**: `/specweave-ado:clone-repos`
+**User**: `/sw-ado:clone-repos`
 
 **Output**:
 ```
@@ -319,12 +319,12 @@ Clone 16 repositories to current directory? (Y/n)
 
    ✓ Clone job started in background (PID: 12345)
 
-   Check progress: /specweave:jobs
-   Kill if needed: /specweave:jobs --kill abc12345
+   Check progress: /sw:jobs
+   Kill if needed: /sw:jobs --kill abc12345
 ```
 
 ### Example 2: Pattern Filter
-**User**: `/specweave-ado:clone-repos --pattern "sw-*"`
+**User**: `/sw-ado:clone-repos --pattern "sw-*"`
 
 **Output**:
 ```
@@ -345,7 +345,7 @@ Clone 8 repositories to current directory? (Y/n)
 ```
 
 ### Example 3: Dry Run
-**User**: `/specweave-ado:clone-repos --dry-run`
+**User**: `/sw-ado:clone-repos --dry-run`
 
 **Output**:
 ```
@@ -361,8 +361,8 @@ Clone 8 repositories to current directory? (Y/n)
 ## Important Notes
 
 - **Background Cloning**: Repositories clone in background (non-blocking)
-- **Progress Tracking**: Check progress with `/specweave:jobs`
-- **Resumable**: Interrupted clones can resume with `/specweave:jobs --resume <id>`
+- **Progress Tracking**: Check progress with `/sw:jobs`
+- **Resumable**: Interrupted clones can resume with `/sw:jobs --resume <id>`
 - **Auth via PAT**: Uses HTTPS clone URLs with PAT authentication
 - **Project-Based Folders**: Repos organized by ADO project: `./<project-name>/<repo-name>/`
   - Project names sanitized for filesystem (lowercase, spaces→hyphens)
@@ -370,16 +370,16 @@ Clone 8 repositories to current directory? (Y/n)
 
 ## Related Commands
 
-- `/specweave:init` - Initial SpecWeave setup (includes repo cloning option)
-- `/specweave:jobs` - Monitor background jobs
-- `/specweave-ado:import-projects` - Import ADO projects with area path mapping
+- `/sw:init` - Initial SpecWeave setup (includes repo cloning option)
+- `/sw:jobs` - Monitor background jobs
+- `/sw-ado:import-projects` - Import ADO projects with area path mapping
 
 ## Error Handling
 
 - **Missing Credentials**: Prompt to run `specweave init` first
 - **Auth Failures**: Check PAT permissions (vso.code_read scope required)
 - **Clone Failures**: Individual repo failures logged, others continue
-- **Network Errors**: Job pauses, resume with `/specweave:jobs --resume`
+- **Network Errors**: Job pauses, resume with `/sw:jobs --resume`
 
 ---
 

package/plugins/specweave-ado/commands/close.md

@@ -1,11 +1,11 @@
 ---
-name: specweave-ado:close
+name: sw-ado:close
 description: Close Azure DevOps work item when increment complete
 ---
 
 # Close ADO Work Item Command
 
-**Usage**: `/specweave-ado:close <increment-id>`
+**Usage**: `/sw-ado:close <increment-id>`
 
 **Purpose**: Close ADO work item and add completion summary
 
@@ -157,7 +157,7 @@ This command requires **both** permissions:
 ### Success
 
 ```
-User: /specweave-ado:close-workitem 0005-payment-integration
+User: /sw-ado:close-workitem 0005-payment-integration
 
 Claude:
 Checking permissions...
@@ -188,7 +188,7 @@ URL: https://dev.azure.com/acme-corp/My%20Project/_workitems/edit/12345
 ### Permission Denied
 
 ```
-User: /specweave-ado:close-workitem 0005
+User: /sw-ado:close-workitem 0005
 
 Claude:
 Checking permissions...
@@ -207,7 +207,7 @@ Update .specweave/config.json to enable these permissions.
 ### Incomplete Increment
 
 ```
-User: /specweave-ado:close-workitem 0005
+User: /sw-ado:close-workitem 0005
 
 Claude:
 Checking permissions...
@@ -234,8 +234,8 @@ Complete remaining tasks:
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:pull` | Pull changes from ADO |
-| `/specweave-ado:push` | Push progress to ADO |
-| `/specweave-ado:sync` | Two-way sync |
-| `/specweave-ado:create` | Create ADO work item |
-| `/specweave-ado:status` | Check sync status |
+| `/sw-ado:pull` | Pull changes from ADO |
+| `/sw-ado:push` | Push progress to ADO |
+| `/sw-ado:sync` | Two-way sync |
+| `/sw-ado:create` | Create ADO work item |
+| `/sw-ado:status` | Check sync status |

package/plugins/specweave-ado/commands/create.md

@@ -1,11 +1,11 @@
 ---
-name: specweave-ado:create
+name: sw-ado:create
 description: Create Azure DevOps work item from SpecWeave increment
 ---
 
 # Create ADO Work Item Command
 
-**Usage**: `/specweave-ado:create <increment-id>`
+**Usage**: `/sw-ado:create <increment-id>`
 
 **Purpose**: Create an Epic, Feature, or User Story in Azure DevOps from a SpecWeave increment
 
@@ -142,7 +142,7 @@ This setting was configured during 'specweave init'.
 ## Example Usage
 
 ```
-User: /specweave-ado:create-workitem 0005-payment-integration
+User: /sw-ado:create-workitem 0005-payment-integration
 
 # If permission granted:
 Claude: Checking ADO permissions...
@@ -174,8 +174,8 @@ Claude: Checking ADO permissions...
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:pull` | Pull changes from ADO |
-| `/specweave-ado:push` | Push progress to ADO |
-| `/specweave-ado:sync` | Two-way sync |
-| `/specweave-ado:status` | Check sync status |
-| `/specweave-ado:close` | Close work item when complete |
+| `/sw-ado:pull` | Pull changes from ADO |
+| `/sw-ado:push` | Push progress to ADO |
+| `/sw-ado:sync` | Two-way sync |
+| `/sw-ado:status` | Check sync status |
+| `/sw-ado:close` | Close work item when complete |

package/plugins/specweave-ado/commands/import-areas.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado:import-areas
+name: sw-ado:import-areas
 description: Import Azure DevOps area paths from a project and map them to SpecWeave projects. Creates 2-level directory structure with area path-based organization.
 ---
 
@@ -10,10 +10,10 @@ You are an Azure DevOps integration expert. Help the user import area paths from
 ## Command Usage
 
 ```bash
-/specweave-ado:import-areas                         # Interactive mode (prompts for project)
-/specweave-ado:import-areas --project MyProduct     # Specific ADO project
-/specweave-ado:import-areas --dry-run               # Preview without creating directories
-/specweave-ado:import-areas --include-children      # Include child area paths
+/sw-ado:import-areas                         # Interactive mode (prompts for project)
+/sw-ado:import-areas --project MyProduct     # Specific ADO project
+/sw-ado:import-areas --dry-run               # Preview without creating directories
+/sw-ado:import-areas --include-children      # Include child area paths
 ```
 
 ## Your Task
@@ -226,8 +226,8 @@ Area paths imported:
     Keywords: infrastructure, ci, cd, terraform
 
 💡 Next steps:
-  1. Use /specweave:switch-project fe to switch active project
-  2. Create increment: /specweave:increment "feature name"
+  1. Use /sw:switch-project fe to switch active project
+  2. Create increment: /sw:increment "feature name"
   3. User stories will auto-sync to the correct area path based on keywords
 
 📖 Documentation: .specweave/docs/internal/architecture/adr/0143-jira-ado-multi-level-project-mapping.md
@@ -237,7 +237,7 @@ Area paths imported:
 
 ### Example 1: Interactive Import
 ```
-User: /specweave-ado:import-areas
+User: /sw-ado:import-areas
 
 You:
 🔷 Azure DevOps Area Path Import
@@ -261,7 +261,7 @@ Mapping to SpecWeave projects:
 
 ### Example 2: Dry Run
 ```
-User: /specweave-ado:import-areas --project MyProduct --dry-run
+User: /sw-ado:import-areas --project MyProduct --dry-run
 
 You:
 🔷 Azure DevOps Area Path Import (DRY RUN)
@@ -281,7 +281,7 @@ No changes made (dry run).
 
 ### Example 3: Already Configured
 ```
-User: /specweave-ado:import-areas
+User: /sw-ado:import-areas
 
 You:
 ⚠️  Area path mapping already exists for project MyProduct
@@ -333,7 +333,7 @@ Available projects you have access to:
   - Infrastructure (DevOps & Infrastructure)
   - Legacy (Legacy Systems)
 
-Tip: Use /specweave-ado:import-areas --project MyProduct
+Tip: Use /sw-ado:import-areas --project MyProduct
 ```
 
 **No area paths found:**
@@ -352,7 +352,7 @@ Suggestions:
 
 ## Related Commands
 
-- `/specweave-ado:import-projects` - Import multiple ADO projects
-- `/specweave-ado:sync` - Sync increments with ADO
-- `/specweave:switch-project` - Switch active SpecWeave project
-- `/specweave:init-multiproject` - Initialize multi-project mode
+- `/sw-ado:import-projects` - Import multiple ADO projects
+- `/sw-ado:sync` - Sync increments with ADO
+- `/sw:switch-project` - Switch active SpecWeave project
+- `/sw:init-multiproject` - Initialize multi-project mode

package/plugins/specweave-ado/commands/import-projects.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado:import-projects
+name: sw-ado:import-projects
 description: Import additional Azure DevOps projects post-init with area path mapping, filtering, and dry-run preview
 ---
 
@@ -21,19 +21,19 @@ This command allows users to import additional Azure DevOps projects **after** i
 
 ```bash
 # Basic import (interactive)
-/specweave-ado:import-projects
+/sw-ado:import-projects
 
 # With area path granularity
-/specweave-ado:import-projects --granularity two-level
+/sw-ado:import-projects --granularity two-level
 
 # Dry-run (preview)
-/specweave-ado:import-projects --dry-run
+/sw-ado:import-projects --dry-run
 
 # Resume interrupted import
-/specweave-ado:import-projects --resume
+/sw-ado:import-projects --resume
 
 # Combined
-/specweave-ado:import-projects --granularity top-level --dry-run
+/sw-ado:import-projects --granularity top-level --dry-run
 ```
 
 ## Your Task
@@ -228,7 +228,7 @@ if (args.resume) {
 ## Examples
 
 ### Example 1: Basic Import with Area Paths
-**User**: `/specweave-ado:import-projects`
+**User**: `/sw-ado:import-projects`
 
 **Output**:
 ```
@@ -277,7 +277,7 @@ Area paths configured:
 ```
 
 ### Example 2: Top-Level Only
-**User**: `/specweave-ado:import-projects --granularity top-level`
+**User**: `/sw-ado:import-projects --granularity top-level`
 
 **Output**:
 ```
@@ -291,7 +291,7 @@ Select area path granularity: top-level (forced via CLI)
 ```
 
 ### Example 3: Dry-Run
-**User**: `/specweave-ado:import-projects --dry-run`
+**User**: `/sw-ado:import-projects --dry-run`
 
 **Output**:
 ```
@@ -315,9 +315,9 @@ Total: 8 projects would be configured
 
 ## Related Commands
 
-- `/specweave:init` - Initial SpecWeave setup
-- `/specweave-ado:sync` - Sync increments with ADO work items
-- `/specweave-ado:refresh-cache` - Clear cached ADO data
+- `/sw:init` - Initial SpecWeave setup
+- `/sw-ado:sync` - Sync increments with ADO work items
+- `/sw-ado:refresh-cache` - Clear cached ADO data
 
 ## Error Handling