specweave 0.33.4 → 0.33.6

package/plugins/specweave/skills/increment-planner/templates/spec-multi-project.md

@@ -8,11 +8,8 @@ created: {{DATE}}
 structure: user-stories
 test_mode: {{TEST_MODE}}
 coverage_target: {{COVERAGE_TARGET}}
-# MANDATORY: Must be RESOLVED values from "specweave context projects" output
-# ⛔ NEVER use {{PROJECT_ID}} or {{BOARD_ID}} placeholders!
-# For 2-level structures: BOTH project AND board are REQUIRED per US
-project: {{RESOLVED_PROJECT}}
-board: {{RESOLVED_BOARD}}
+# NOTE: project:/board: fields REMOVED per ADR-0140 (v0.35.0+)
+# Project and Board are now resolved from per-US **Project**: and **Board**: fields
 multi_project: true
 projects:
   - id: {{RESOLVED_PROJECT_FE}}
@@ -32,17 +29,10 @@ projects:
 ## User Stories
 
 <!--
-⚠️ MANDATORY RESOLUTION (v0.34.0+):
-1. Run: specweave context projects
-2. Parse JSON output:
-   - level 1: projects[].id gives valid project IDs
-   - level 2: projects[].id + boardsByProject[project][].id gives project AND board IDs
-3. Replace ALL placeholders with actual IDs from step 2
-4. Each US MUST have **Project**: (and **Board**: for 2-level) with RESOLVED values
-
-❌ FORBIDDEN: Using {{PROJECT_ID}}, {{BOARD_ID}} placeholders
-❌ FORBIDDEN: Inventing project/board names
-✅ REQUIRED: Use ONLY IDs from "specweave context projects" output
+📋 Per-US **Project**: and **Board**: fields (v0.35.0+ - ADR-0140):
+- Each US MUST specify **Project**: field with resolved value
+- For 2-level structures: Each US MUST also specify **Board**: field
+- Run: specweave context projects - to get valid project/board IDs
 -->
 
 ### Frontend Stories

package/plugins/specweave/skills/increment-planner/templates/spec-single-project.md

@@ -8,9 +8,8 @@ created: {{DATE}}
 structure: user-stories
 test_mode: {{TEST_MODE}}
 coverage_target: {{COVERAGE_TARGET}}
-# MANDATORY: Must be a RESOLVED value from "specweave context projects" output
-# ⛔ NEVER use {{PROJECT_ID}} placeholder - always resolve BEFORE creating spec.md!
-project: {{RESOLVED_PROJECT}}
+# NOTE: project: field REMOVED per ADR-0140 (v0.35.0+)
+# Project is now resolved from per-US **Project**: fields or config.project.name
 ---
 
 # Feature: {{FEATURE_TITLE}}
@@ -22,15 +21,10 @@ project: {{RESOLVED_PROJECT}}
 ## User Stories
 
 <!--
-⚠️ MANDATORY RESOLUTION (v0.34.0+):
-1. Run: specweave context projects
-2. Parse JSON: projects[].id gives valid project IDs
-3. Replace {{RESOLVED_PROJECT}} with actual ID from step 2
-4. Each US MUST have **Project**: field with RESOLVED value
-
-❌ FORBIDDEN: Using {{PROJECT_ID}} placeholder
-❌ FORBIDDEN: Inventing project names
-✅ REQUIRED: Use ONLY IDs from "specweave context projects" output
+📋 Per-US **Project**: field (v0.35.0+ - ADR-0140):
+- In single-project mode: **Project**: can use config.project.name (auto-resolved)
+- In multi-project mode: Each US MUST specify its **Project**: field
+- Run: specweave context projects - to get valid project IDs
 -->
 
 ### US-001: [Story Title] (P1)

package/plugins/specweave/skills/increment-quality-judge-v2/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: increment-quality-judge-v2
-description: Enhanced AI-powered quality assessment with RISK SCORING (BMAD pattern) and quality gate decisions. Evaluates specifications, plans, and tests for clarity, testability, completeness, feasibility, maintainability, edge cases, and RISKS. Provides PASS/CONCERNS/FAIL decisions. Activates for validate quality, quality check, assess spec, evaluate increment, spec review, quality score, risk assessment, qa check, quality gate, /specweave:qa command.
+description: Enhanced AI-powered quality assessment with RISK SCORING (BMAD pattern) and quality gate decisions. Evaluates specifications, plans, and tests for clarity, testability, completeness, feasibility, maintainability, edge cases, and RISKS. Provides PASS/CONCERNS/FAIL decisions. Activates for validate quality, quality check, assess spec, evaluate increment, spec review, quality score, risk assessment, qa check, quality gate, /sw:qa command.
 allowed-tools: Read, Grep, Glob
 ---
 
@@ -60,7 +60,7 @@ This is a **skill** that auto-activates when you discuss quality assessment. To
 specweave qa 0001 --pre
 
 # Or use the slash command
-/specweave:qa 0001
+/sw:qa 0001
 ```
 
 The skill provides guidance and documentation. The CLI handles execution.
@@ -360,7 +360,7 @@ Would you like to:
 ### Quick Mode (Default)
 
 ```
-User: /specweave:qa 0001
+User: /sw:qa 0001
 
 Step 1: Rule-based validation (120 checks) - FREE, FAST
 ├── If FAILED → Stop, show errors
@@ -377,7 +377,7 @@ Output: Enhanced report with risks and gate decision
 ### Pre-Implementation Mode
 
 ```
-User: /specweave:qa 0001 --pre
+User: /sw:qa 0001 --pre
 
 Checks:
 ✅ Spec quality (clarity, testability, completeness)
@@ -391,7 +391,7 @@ Gate decision before implementation starts
 ### Quality Gate Mode
 
 ```
-User: /specweave:qa 0001 --gate
+User: /sw:qa 0001 --gate
 
 Comprehensive checks:
 ✅ All pre-implementation checks
@@ -553,4 +553,4 @@ gate_decision = decide({
 
 **Version**: 2.0.0
 **Since**: v0.8.0
-**Related**: /specweave:qa command, QAOrchestrator agent (v0.9.0)
+**Related**: /sw:qa command, QAOrchestrator agent (v0.9.0)

package/plugins/specweave/skills/increment-work-router/SKILL.md

@@ -60,7 +60,7 @@ This skill activates when user expresses **implementation/continuation intent**:
 - "Plan a new feature" → increment-planner
 
 **Already in Workflow**:
-- User is already executing `/specweave:do`
+- User is already executing `/sw:do`
 - Increment planning is in progress
 - Another skill is handling the request
 
@@ -117,9 +117,9 @@ Active: 0031-user-authentication-system
 ✅ High match → Auto-resume:
 
 "I see you have an active increment for user authentication (0031).
-Resuming work on that increment now with /specweave:do..."
+Resuming work on that increment now with /sw:do..."
 
-[Automatically invokes /specweave:do]
+[Automatically invokes /sw:do]
 ```
 
 **Scenario B: Unrelated to active increment**
@@ -153,9 +153,9 @@ I'm going to create a SpecWeave increment with:
 - Technical plan (HOW)
 - Task breakdown (STEPS with embedded tests)
 
-Creating increment now with /specweave:increment..."
+Creating increment now with /sw:increment..."
 
-[Automatically invokes /specweave:increment "user authentication"]
+[Automatically invokes /sw:increment "user authentication"]
 ```
 
 **Scenario D: Multiple active increments**
@@ -184,7 +184,7 @@ Progress: 3/10 tasks complete (30%)
 
 Next task: T-004 Implement password hashing
 
-[Automatically invokes /specweave:do]"
+[Automatically invokes /sw:do]"
 ```
 
 ## Integration Architecture
@@ -203,14 +203,14 @@ increment-work-router (detects intent)
 └─────┬─────────────┴──────┬───────────┴──────┬─────────┘
       │                    │                  │
       ↓                    ↓                  ↓
-/specweave:do        Ask to select    /specweave:increment
+/sw:do        Ask to select    /sw:increment
 (auto-resume)        (clarify)        (create new)
 ```
 
 **Calls:**
-- `/specweave:do` - Resume active increment
-- `/specweave:increment` - Create new increment
-- `/specweave:status` - Check increment state (if needed)
+- `/sw:do` - Resume active increment
+- `/sw:increment` - Create new increment
+- `/sw:status` - Check increment state (if needed)
 
 **Called By:**
 - Automatically when implementation intent detected
@@ -220,11 +220,11 @@ increment-work-router (detects intent)
 
 | User Intent | Active Increments | Relevance | Action |
 |-------------|------------------|-----------|--------|
-| "Implement auth" | 1 (auth-related) | High (>70%) | Auto `/specweave:do` |
+| "Implement auth" | 1 (auth-related) | High (>70%) | Auto `/sw:do` |
 | "Implement auth" | 1 (unrelated) | Low (<40%) | Ask: New or add to current? |
-| "Implement auth" | 0 | N/A | Auto `/specweave:increment` |
+| "Implement auth" | 0 | N/A | Auto `/sw:increment` |
 | "Implement auth" | 2+ | N/A | Ask which increment |
-| "Let's continue" | 1 | N/A | Auto `/specweave:do` |
+| "Let's continue" | 1 | N/A | Auto `/sw:do` |
 | "Let's continue" | 2+ | N/A | Ask which increment |
 | "Let's continue" | 0 | N/A | "No active increment. What should we build?" |
 
@@ -304,9 +304,9 @@ Implement JWT token refresh
 "I see you have an active increment for user authentication (0031).
 Task T-005 'Implement JWT token refresh' is already in your plan.
 
-Resuming increment 0031 now with /specweave:do...
+Resuming increment 0031 now with /sw:do...
 
-[Automatically invokes /specweave:do]
+[Automatically invokes /sw:do]
 ```
 
 ### Example 2: Create New (No Active Increment)
@@ -335,9 +335,9 @@ I'm going to create a SpecWeave increment with:
 - Technical plan (API integration, webhooks, security)
 - Task breakdown (implementation steps with tests)
 
-Creating increment now with /specweave:increment...
+Creating increment now with /sw:increment...
 
-[Automatically invokes /specweave:increment "payment processing with Stripe"]
+[Automatically invokes /sw:increment "payment processing with Stripe"]
 ```
 
 ### Example 3: Unrelated Request (Ask)
@@ -403,7 +403,7 @@ Let's continue working
 
 Which one would you like to work on?"
 
-[Wait for user selection, then invoke /specweave:do {selected-id}]
+[Wait for user selection, then invoke /sw:do {selected-id}]
 ```
 
 ### Example 5: Vague Intent + Single Active (Auto-Resume)
@@ -430,7 +430,7 @@ Progress: 3/10 tasks complete (30%)
 
 Next task: **T-004 Implement password hashing**
 
-[Automatically invokes /specweave:do]"
+[Automatically invokes /sw:do]"
 ```
 
 ## Opt-Out Mechanism
@@ -438,13 +438,13 @@ Next task: **T-004 Implement password hashing**
 Users can override auto-routing with explicit instructions:
 - "Don't resume, create new" → Forces new increment
 - "Just discuss first" → Regular conversation
-- "Plan without implementing" → Routes to `/specweave:increment` only
-- "Show me the current state" → Uses `/specweave:status` instead
+- "Plan without implementing" → Routes to `/sw:increment` only
+- "Show me the current state" → Uses `/sw:status` instead
 
 ## Success Criteria
 
 - ✅ Users can say "implement X" and work starts automatically
-- ✅ Smart routing to active increments (no manual `/specweave:do`)
+- ✅ Smart routing to active increments (no manual `/sw:do`)
 - ✅ Detects unrelated requests and prevents scope creep
 - ✅ No "which increment?" confusion (auto-handles single active)
 - ✅ Clear choices when ambiguous (multiple active or unrelated)
@@ -454,7 +454,7 @@ Users can override auto-routing with explicit instructions:
 
 - **project-kickstarter**: For NEW project descriptions (complements, doesn't overlap)
 - **increment-planner**: For creating increment structure (invoked by this skill)
-- **specweave-detector**: For checking SpecWeave context
+- **detector**: For checking SpecWeave context
 
 ---
 

package/plugins/specweave/skills/instant-status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: instant-status
-description: Instant status commands that bypass LLM processing. Execute scripts directly for /specweave:status, /specweave:progress, /specweave:jobs. Activates for specweave status, specweave progress, specweave jobs, increment status, show status, show progress, background jobs, job status.
+description: Instant status commands that bypass LLM processing. Execute scripts directly for /sw:status, /sw:progress, /sw:jobs. Activates for specweave status, specweave progress, specweave jobs, increment status, show status, show progress, background jobs, job status.
 ---
 
 # Instant Status Commands
@@ -11,9 +11,9 @@ These commands need **NO LLM reasoning** - execute scripts directly for instant
 
 | Command | Script | Purpose |
 |---------|--------|---------|
-| `/specweave:status` | `bash plugins/specweave/scripts/read-status.sh` | Increment status overview |
-| `/specweave:progress` | `bash plugins/specweave/scripts/read-progress.sh` | Task completion progress |
-| `/specweave:jobs` | `bash plugins/specweave/scripts/read-jobs.sh` | Background job status |
+| `/sw:status` | `bash plugins/specweave/scripts/read-status.sh` | Increment status overview |
+| `/sw:progress` | `bash plugins/specweave/scripts/read-progress.sh` | Task completion progress |
+| `/sw:jobs` | `bash plugins/specweave/scripts/read-jobs.sh` | Background job status |
 
 ## CRITICAL: Direct Execution Required
 
@@ -27,15 +27,15 @@ When user requests these commands:
 ### Example Execution
 
 ```bash
-# User types: /specweave:status
+# User types: /sw:status
 # You execute:
 bash plugins/specweave/scripts/read-status.sh
 
-# User types: /specweave:progress
+# User types: /sw:progress
 # You execute:
 bash plugins/specweave/scripts/read-progress.sh
 
-# User types: /specweave:jobs
+# User types: /sw:jobs
 # You execute:
 bash plugins/specweave/scripts/read-jobs.sh
 ```

package/plugins/specweave/skills/plugin-validator/SKILL.md

@@ -33,8 +33,8 @@ This skill ensures that your SpecWeave environment is properly configured with a
 - During: `specweave init` (initial setup only)
 
 ❌ **Does NOT auto-activate for**:
-- `/specweave:increment` commands
-- `/specweave:do` commands
+- `/sw:increment` commands
+- `/sw:do` commands
 - Any other workflow commands
 - Reason: Prevents false positive errors when plugins are installed but detection fails
 
@@ -103,7 +103,7 @@ This skill ensures that your SpecWeave environment is properly configured with a
 
 **Scenario**: You cloned a project to a new VM and want to start working.
 
-**Action**: Run `/specweave:increment "Add authentication"`
+**Action**: Run `/sw:increment "Add authentication"`
 
 **What Happens**:
 ```
@@ -124,7 +124,7 @@ This skill ensures that your SpecWeave environment is properly configured with a
 
 **Scenario**: You're adding a new feature that uses GitHub and React.
 
-**Action**: Run `/specweave:increment "Add GitHub sync with React UI"`
+**Action**: Run `/sw:increment "Add GitHub sync with React UI"`
 
 **What Happens**:
 ```
@@ -307,15 +307,15 @@ specweave validate-plugins --auto-install --context="Deploy to Kubernetes" --ver
 
 **All SpecWeave commands validate plugins** before execution (STEP 0):
 
-- `/specweave:increment` - Validates before PM agent runs
-- `/specweave:do` - Validates before task execution
-- `/specweave:next` - Validates before next increment
-- `/specweave:done` - Validates before completion
+- `/sw:increment` - Validates before PM agent runs
+- `/sw:do` - Validates before task execution
+- `/sw:next` - Validates before next increment
+- `/sw:done` - Validates before completion
 - ... (all 22 commands)
 
 **Workflow**:
 ```
-User: /specweave:increment "Add feature"
+User: /sw:increment "Add feature"
         ↓
    [STEP 0: Plugin Validation]
         ↓ (only proceeds if valid)

package/plugins/specweave/skills/pm-closure-validation/SKILL.md

@@ -531,10 +531,10 @@ When approving closure, summarize what was delivered:
 - **architect**: Designs technical solution (plan.md)
 
 ### Commands
-- `/specweave:done {increment-id}` - Trigger PM closure validation
-- `/specweave:status {increment-id}` - Check increment status
-- `/specweave:validate {increment-id}` - Run validation checks
-- `/specweave:check-tests {increment-id}` - Validate test coverage
+- `/sw:done {increment-id}` - Trigger PM closure validation
+- `/sw:status {increment-id}` - Check increment status
+- `/sw:validate {increment-id}` - Run validation checks
+- `/sw:check-tests {increment-id}` - Validate test coverage
 
 ---
 

package/plugins/specweave/skills/progress-sync/SKILL.md

@@ -1,15 +1,15 @@
 ---
 name: progress-sync
-description: Comprehensive progress synchronization expert. Explains when and how to use /specweave:sync-progress for multi-system sync (tasks → docs → external tools). Activates for sync progress, update progress, sync everything, sync all systems, sync to GitHub, sync to JIRA, how to sync, progress synchronization, multi-system sync.
+description: Comprehensive progress synchronization expert. Explains when and how to use /sw:sync-progress for multi-system sync (tasks → docs → external tools). Activates for sync progress, update progress, sync everything, sync all systems, sync to GitHub, sync to JIRA, how to sync, progress synchronization, multi-system sync.
 ---
 
 # Progress Sync Expert
 
-I'm the comprehensive progress synchronization expert for SpecWeave. I help you understand and use the `/specweave:sync-progress` command for end-to-end progress synchronization.
+I'm the comprehensive progress synchronization expert for SpecWeave. I help you understand and use the `/sw:sync-progress` command for end-to-end progress synchronization.
 
 ---
 
-## What is /specweave:sync-progress?
+## What is /sw:sync-progress?
 
 **The "single button" to sync progress across all systems**:
 
@@ -19,26 +19,26 @@ tasks.md → spec.md ACs → living docs → external tools (GitHub/JIRA/ADO)
 
 **One command, complete synchronization**:
 ```bash
-/specweave:sync-progress
+/sw:sync-progress
 ```
 
 ---
 
 ## When to Use This Command
 
-### ✅ Use /specweave:sync-progress when:
+### ✅ Use /sw:sync-progress when:
 
 1. **After completing tasks**: You've marked tasks as done in tasks.md and want to sync everywhere
-2. **Before closing increment**: Final sync before `/specweave:done` to ensure all systems in sync
+2. **Before closing increment**: Final sync before `/sw:done` to ensure all systems in sync
 3. **Progress check**: Want to update status line and external tools with latest progress
 4. **After bulk task completion**: Completed multiple tasks, sync all at once
 5. **Manual sync trigger**: Hooks didn't fire or you want to force a sync
 
 ### ❌ Don't use when:
 
-1. **Only want to sync ACs**: Use `/specweave:sync-acs` instead (faster, more targeted)
-2. **Only want to sync docs**: Use `/specweave:sync-specs` instead
-3. **Only want to sync GitHub**: Use `/specweave-github:sync` instead
+1. **Only want to sync ACs**: Use `/sw:sync-acs` instead (faster, more targeted)
+2. **Only want to sync docs**: Use `/sw:sync-specs` instead
+3. **Only want to sync GitHub**: Use `/sw-github:sync` instead
 4. **Increment not started**: No tasks to sync yet
 
 ---
@@ -78,7 +78,7 @@ Phase 4: Status Line Cache
 
 ```bash
 # Single command syncs everything
-/specweave:sync-progress
+/sw:sync-progress
 ```
 
 **What happens**:
@@ -96,13 +96,13 @@ Phase 4: Status Line Cache
 
 ```bash
 # Final sync before closure
-/specweave:sync-progress 0053
+/sw:sync-progress 0053
 
 # Then close increment
-/specweave:done 0053
+/sw:done 0053
 ```
 
-**Why important**: `/specweave:done` validates completion. Final sync ensures:
+**Why important**: `/sw:done` validates completion. Final sync ensures:
 - All ACs marked complete
 - All user stories synced
 - All GitHub issues closed
@@ -116,7 +116,7 @@ Phase 4: Status Line Cache
 
 ```bash
 # Preview mode
-/specweave:sync-progress 0053 --dry-run
+/sw:sync-progress 0053 --dry-run
 ```
 
 **Output**:
@@ -140,7 +140,7 @@ Run without --dry-run to execute sync.
 
 ```bash
 # Skip external tools
-/specweave:sync-progress 0053 --no-github --no-jira --no-ado
+/sw:sync-progress 0053 --no-github --no-jira --no-ado
 ```
 
 **What syncs**:
@@ -164,10 +164,10 @@ Run without --dry-run to execute sync.
 **Combine flags**:
 ```bash
 # Dry-run with no external tools
-/specweave:sync-progress --dry-run --no-github
+/sw:sync-progress --dry-run --no-github
 
 # Force sync, skip GitHub
-/specweave:sync-progress --force --no-github
+/sw:sync-progress --force --no-github
 ```
 
 ---
@@ -176,14 +176,14 @@ Run without --dry-run to execute sync.
 
 | Command | Scope | When to Use |
 |---------|-------|-------------|
-| `/specweave:sync-acs` | Tasks → ACs only | Quick AC update |
-| `/specweave:sync-specs` | Spec → Docs only | After spec changes |
-| `/specweave-github:sync` | Docs → GitHub only | GitHub-only sync |
-| `/specweave:sync-progress` | **Tasks → Docs → External** | **Complete sync** ✅ |
+| `/sw:sync-acs` | Tasks → ACs only | Quick AC update |
+| `/sw:sync-specs` | Spec → Docs only | After spec changes |
+| `/sw-github:sync` | Docs → GitHub only | GitHub-only sync |
+| `/sw:sync-progress` | **Tasks → Docs → External** | **Complete sync** ✅ |
 
 **Rule of thumb**:
 - Need **targeted sync** → Use specific command (`sync-acs`, `sync-specs`)
-- Need **complete sync** → Use `/specweave:sync-progress` ✅
+- Need **complete sync** → Use `/sw:sync-progress` ✅
 
 ---
 
@@ -193,10 +193,10 @@ Run without --dry-run to execute sync.
 
 ```bash
 # Explicit increment ID
-/specweave:sync-progress 0053
+/sw:sync-progress 0053
 
 # Auto-detect from active increment
-/specweave:sync-progress
+/sw:sync-progress
 ```
 
 **How auto-detection works**:
@@ -253,7 +253,7 @@ The command checks `.specweave/config.json` for:
 **Fix**:
 ```bash
 # Provide increment ID explicitly
-/specweave:sync-progress 0053
+/sw:sync-progress 0053
 ```
 
 ---
@@ -268,10 +268,10 @@ The command checks `.specweave/config.json` for:
 **Fix**:
 ```bash
 # Embed ACs from living docs into spec.md
-/specweave:embed-acs 0053
+/sw:embed-acs 0053
 
 # Then retry sync
-/specweave:sync-progress 0053
+/sw:sync-progress 0053
 ```
 
 **Why this happens**: spec.md missing inline ACs (ADR-0064 requirement).
@@ -289,7 +289,7 @@ The command checks `.specweave/config.json` for:
 
 ```bash
 # Retry GitHub sync only (when rate limit resets)
-/specweave-github:sync 0053
+/sw-github:sync 0053
 ```
 
 ---
@@ -300,24 +300,24 @@ The command checks `.specweave/config.json` for:
 
 ```bash
 # 1. Plan increment
-/specweave:increment "Safe feature deletion"
+/sw:increment "Safe feature deletion"
 
 # 2. Execute tasks
-/specweave:do
+/sw:do
 
 # [Complete tasks manually or via sub-agents...]
 
 # 3. Sync progress after each batch of tasks
-/specweave:sync-progress
+/sw:sync-progress
 
 # 4. Final sync before closure
-/specweave:sync-progress 0053
+/sw:sync-progress 0053
 
 # 5. Validate quality
-/specweave:validate 0053 --quality
+/sw:validate 0053 --quality
 
 # 6. Close increment
-/specweave:done 0053
+/sw:done 0053
 ```
 
 ---
@@ -327,7 +327,7 @@ The command checks `.specweave/config.json` for:
 ### ✅ DO:
 
 1. **Sync after task batches**: Complete 3-5 tasks → sync → continue
-2. **Final sync before closure**: Ensure 100% sync before `/specweave:done`
+2. **Final sync before closure**: Ensure 100% sync before `/sw:done`
 3. **Use dry-run first**: Preview changes with `--dry-run`
 4. **Check external tools**: Verify GitHub/JIRA after sync
 5. **Review status line**: Ensure completion % updated correctly
@@ -335,7 +335,7 @@ The command checks `.specweave/config.json` for:
 ### ❌ DON'T:
 
 1. **Don't sync for every task**: Batching is more efficient
-2. **Don't skip final sync**: Always sync before `/specweave:done`
+2. **Don't skip final sync**: Always sync before `/sw:done`
 3. **Don't ignore warnings**: AC sync warnings indicate missing ACs
 4. **Don't force sync without understanding**: `--force` bypasses validation
 5. **Don't sync before tasks complete**: Sync when progress actually changed
@@ -349,13 +349,13 @@ The command checks `.specweave/config.json` for:
 ```
 Problem: Manual multi-step sync is error-prone
   1. Update spec.md ACs manually
-  2. Run /specweave:sync-specs
-  3. Run /specweave-github:sync
-  4. Run /specweave:update-status
+  2. Run /sw:sync-specs
+  3. Run /sw-github:sync
+  4. Run /sw:update-status
   5. Check each system for correctness
 
 Solution: Single command orchestrates all steps
-  /specweave:sync-progress → Does all 4 steps automatically
+  /sw:sync-progress → Does all 4 steps automatically
 ```
 
 **Benefits**:
@@ -374,10 +374,10 @@ Solution: Single command orchestrates all steps
 **ADR**: None yet (new feature)
 
 **Context**: Before this command, users had to manually:
-1. Run `/specweave:sync-acs`
-2. Run `/specweave:sync-specs`
-3. Run `/specweave-github:sync`
-4. Run `/specweave:update-status`
+1. Run `/sw:sync-acs`
+2. Run `/sw:sync-specs`
+3. Run `/sw-github:sync`
+4. Run `/sw:update-status`
 
 Now: **One command does all 4 steps** ✅
 
@@ -385,13 +385,13 @@ Now: **One command does all 4 steps** ✅
 
 ## Related Commands
 
-- `/specweave:sync-acs` - Sync tasks → ACs only
-- `/specweave:sync-specs` - Sync spec → living docs only
-- `/specweave:sync-tasks` - Sync external → tasks (bidirectional)
-- `/specweave-github:sync` - Sync docs → GitHub only
-- `/specweave-jira:sync` - Sync docs → JIRA only
-- `/specweave-ado:sync` - Sync docs → ADO only
-- `/specweave:update-status` - Update status line cache
+- `/sw:sync-acs` - Sync tasks → ACs only
+- `/sw:sync-specs` - Sync spec → living docs only
+- `/sw:sync-tasks` - Sync external → tasks (bidirectional)
+- `/sw-github:sync` - Sync docs → GitHub only
+- `/sw-jira:sync` - Sync docs → JIRA only
+- `/sw-ado:sync` - Sync docs → ADO only
+- `/sw:update-status` - Update status line cache
 
 ---