specweave 0.33.4 → 0.33.6

package/plugins/specweave/skills/project-kickstarter/SKILL.md

@@ -10,7 +10,7 @@ description: Proactively detects product/project descriptions and guides users t
 The project-kickstarter skill is a **generic, pattern-based detection system** that:
 - ✅ Works for ANY product/project (not hardcoded for specific products)
 - ✅ Detects structural patterns (features list, tech stack, timeline, etc.)
-- ✅ Integrates with specweave-detector to check SpecWeave context
+- ✅ Integrates with detector to check SpecWeave context
 - ✅ Routes to appropriate SpecWeave workflow automatically
 
 **Not product-specific!** This skill recognizes the STRUCTURE of product descriptions, not specific products.
@@ -105,7 +105,7 @@ SpecWeave works best when we start with a proper increment plan. I'm going to:
 
 Let's start: [Ask 1 clarifying question if needed, otherwise proceed]"
 
-[Automatically invoke /specweave:inc or spec-driven-brainstorming]
+[Automatically invoke /sw:inc or spec-driven-brainstorming]
 ```
 
 **Medium Confidence:**
@@ -188,7 +188,7 @@ project-kickstarter:
 6. Checks: specweave-github plugin installed? Yes
 7. Tests: GitHub API connection? ✅ Success
 8. Saves: externalPM.tool = "github" to config
-9. Creates increment: /specweave:inc "User authentication"
+9. Creates increment: /sw:inc "User authentication"
 10. Auto-creates: GitHub Issue #42 linked to increment
 ```
 
@@ -198,7 +198,7 @@ project-kickstarter:
 
 Based on clarity of requirements:
 
-- **Clear requirements** (detailed features, tech stack known) → `/specweave:inc` directly
+- **Clear requirements** (detailed features, tech stack known) → `/sw:inc` directly
 - **Unclear requirements** (vague features, tech stack uncertain) → `spec-driven-brainstorming` first
 
 ## Examples
@@ -250,9 +250,9 @@ I'm going to use SpecWeave's increment planning process to:
 
 Since you've provided the tech stack (.NET 8 + Next.js 14+), I'll structure this as a full-stack increment.
 
-Creating increment now with /specweave:inc...
+Creating increment now with /sw:inc...
 
-[Invokes /specweave:inc "RosterSync team scheduling SaaS"]
+[Invokes /sw:inc "RosterSync team scheduling SaaS"]
 ```
 
 ### Example 2: Clarify Then Route (Medium Confidence)
@@ -317,7 +317,7 @@ This is a technical question, not a project description. Let other skills or gen
 
 **Workflow**:
 ```
-User message → specweave-detector (checks .specweave/ exists)
+User message → detector (checks .specweave/ exists)
                     ↓
               project-kickstarter (pattern detection)
                     ↓
@@ -325,12 +325,12 @@ User message → specweave-detector (checks .specweave/ exists)
                     ↓ YES
          [Calculate confidence with SpecWeave context bonus]
                     ↓
-         [Route to /specweave:inc or spec-driven-brainstorming]
+         [Route to /sw:inc or spec-driven-brainstorming]
 ```
 
 **Calls:**
-- `specweave-detector` - Checks if .specweave/ directory exists (SpecWeave context)
-- `/specweave:inc` - For clear requirements (high confidence)
+- `detector` - Checks if .specweave/ directory exists (SpecWeave context)
+- `/sw:inc` - For clear requirements (high confidence)
 - Spec-driven brainstorming - For unclear requirements (medium confidence)
 - Planning workflow - Directly if enough detail provided
 
@@ -355,7 +355,7 @@ Users can override auto-routing with explicit instructions:
 ## Success Criteria
 
 - ✅ Users with product descriptions are automatically guided to increment planning
-- ✅ No "I forgot to use /specweave:inc" scenarios
+- ✅ No "I forgot to use /sw:inc" scenarios
 - ✅ Confidence >80% routes immediately (no friction)
 - ✅ Confidence 50-80% clarifies then routes (1-2 questions max)
 - ✅ Confidence <50% doesn't activate (avoids false positives)

package/plugins/specweave/skills/role-orchestrator/README.md

@@ -152,7 +152,7 @@ const roleRules = {
 
 ## Integration
 
-**Called by**: specweave-detector (when new increment created)
+**Called by**: detector (when new increment created)
 
 **Calls**: PM, Architect, QA, DevOps, Security agents as needed
 

package/plugins/specweave/skills/role-orchestrator/SKILL.md

@@ -433,16 +433,16 @@ Total estimated time: 35 minutes
 
 ```bash
 # Check status
-/specweave:status
+/sw:status
 
 # Sync to external tools
-/specweave:sync-progress 0001
+/sw:sync-progress 0001
 
 # Validate quality
-/specweave:qa 0001
+/sw:qa 0001
 
 # Close increment
-/specweave:done 0001
+/sw:done 0001
 ```
 
 ---

package/plugins/specweave/skills/smart-reopen-detector/SKILL.md

@@ -47,7 +47,7 @@ Found 2 related item(s) in recent work:
    Matched: github, sync
 
 💡 Suggested action:
-   /specweave:reopen 0031-external-tool-status-sync --reason "GitHub sync not working"
+   /sw:reopen 0031-external-tool-status-sync --reason "GitHub sync not working"
 
 Would you like me to:
 1. Reopen the entire increment (checks WIP limits)
@@ -79,7 +79,7 @@ Found 3 related item(s) in recent work:
    Matched: authentication
 
 💡 Suggested action:
-   /specweave:reopen 0025-user-auth --task T-012 --reason "Authentication broken after deployment"
+   /sw:reopen 0025-user-auth --task T-012 --reason "Authentication broken after deployment"
 
 ⚠️  Note: Increment 0025 was completed 3 days ago. Consider checking deployment config first.
 ```
@@ -131,7 +131,7 @@ I assign relevance scores using:
 I provide:
 - Top matches (up to 5)
 - Relevance scores
-- Suggested `/specweave:reopen` command
+- Suggested `/sw:reopen` command
 - WIP limit warnings (if applicable)
 
 ## Smart Suggestions
@@ -139,25 +139,25 @@ I provide:
 ### For Increments
 ```bash
 # Reopen entire increment
-/specweave:reopen 0031-external-tool-status-sync --reason "GitHub sync failing"
+/sw:reopen 0031-external-tool-status-sync --reason "GitHub sync failing"
 
 # Check WIP limits first (recommended)
-/specweave:status
+/sw:status
 ```
 
 ### For Specific Tasks
 ```bash
 # Reopen single task (surgical fix)
-/specweave:reopen 0031 --task T-003 --reason "GitHub API 500 error"
+/sw:reopen 0031 --task T-003 --reason "GitHub API 500 error"
 
 # Reopen multiple related tasks
-/specweave:reopen 0031 --user-story US-001 --reason "All GitHub features broken"
+/sw:reopen 0031 --user-story US-001 --reason "All GitHub features broken"
 ```
 
 ### Force Reopen (Bypass WIP Limits)
 ```bash
 # Use --force for critical production issues
-/specweave:reopen 0031 --force --reason "Production down, critical fix needed"
+/sw:reopen 0031 --force --reason "Production down, critical fix needed"
 ```
 
 ## WIP Limit Awareness
@@ -175,26 +175,26 @@ Before suggesting increment reopen, I check:
    Reopening 0031-external-tool-status-sync will EXCEED the limit!
 
    Options:
-   1. Pause another feature first: /specweave:pause 0030
-   2. Complete another feature: /specweave:done 0029
+   1. Pause another feature first: /sw:pause 0030
+   2. Complete another feature: /sw:done 0029
    3. Force reopen (not recommended): --force
 ```
 
 ## Integration with Commands
 
 I work seamlessly with:
-- `/specweave:reopen` - Execute reopen action
-- `/specweave:status` - Check WIP limits
-- `/specweave:progress` - See increment progress
-- `/specweave:pause` - Pause another increment to make room
+- `/sw:reopen` - Execute reopen action
+- `/sw:status` - Check WIP limits
+- `/sw:progress` - See increment progress
+- `/sw:pause` - Pause another increment to make room
 
 ## When NOT to Use
 
 I don't activate for:
 - ❌ General questions about code
-- ❌ Feature requests (use `/specweave:increment`)
+- ❌ Feature requests (use `/sw:increment`)
 - ❌ Documentation questions
-- ❌ Status inquiries (use `/specweave:status`)
+- ❌ Status inquiries (use `/sw:status`)
 
 I **only** activate when you explicitly report something is broken/not working.
 
@@ -240,5 +240,5 @@ I'm successful when:
 ---
 
 **Auto-loads when**: You report issues with recently completed work
-**Commands**: `/specweave:reopen`, `/specweave:status`
+**Commands**: `/sw:reopen`, `/sw:status`
 **Related Skills**: `increment-planner`, `tdd-workflow`

package/plugins/specweave/skills/spec-generator/SKILL.md

@@ -8,7 +8,7 @@ description: Generates comprehensive specifications (spec.md, plan.md, tasks.md
 **Purpose**: Automatically generate comprehensive specification documentation (spec.md, plan.md, tasks.md with embedded tests) for SpecWeave increments using proven templates and flexible, context-aware structure.
 
 **When to Use**:
-- Creating new increments (`/specweave:inc`)
+- Creating new increments (`/sw:inc`)
 - Planning features or products
 - Generating structured documentation
 - Converting ideas into actionable specs
@@ -345,7 +345,7 @@ END IF
 
 ### Example 1: Simple Feature
 ```
-User: /specweave:inc "Add dark mode toggle to settings"
+User: /sw:inc "Add dark mode toggle to settings"
 
 Spec Generator:
 ✓ Detected: Frontend feature (UI component)
@@ -361,7 +361,7 @@ Generating specifications...
 
 ### Example 2: Complex System
 ```
-User: /specweave:inc "Multi-tenant SaaS platform with billing"
+User: /sw:inc "Multi-tenant SaaS platform with billing"
 
 Spec Generator:
 ✓ Detected: New product (SaaS, multi-tenant, payments)
@@ -377,7 +377,7 @@ Generating specifications...
 
 ### Example 3: Bug Fix
 ```
-User: /specweave:inc "Fix race condition in user session handling"
+User: /sw:inc "Fix race condition in user session handling"
 
 Spec Generator:
 ✓ Detected: Bug fix (concurrency issue)
@@ -393,9 +393,9 @@ Generating specifications...
 
 ---
 
-## Integration with /specweave:inc
+## Integration with /sw:inc
 
-The Spec Generator is automatically invoked by `/specweave:inc`:
+The Spec Generator is automatically invoked by `/sw:inc`:
 
 1. **User Intent Analysis**:
    - Analyze increment description

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
 
 ---