specweave 0.33.5 → 0.34.0

package/plugins/specweave/skills/external-sync-wizard/SKILL.md

@@ -121,7 +121,7 @@ Best for: Migrating from GitHub-first workflow to SpecWeave
 
 **4. Manual sync only**
 ```
-Use /specweave-github:sync command when needed
+Use /sw-github:sync command when needed
 
 Features:
 - No automatic sync via hooks
@@ -148,7 +148,7 @@ GitHub ↔ Jira
 
 **1. Yes, auto-create (Recommended)**
 ```
-Every /specweave:increment creates a GitHub issue automatically
+Every /sw:increment creates a GitHub issue automatically
 
 Benefits:
 - Immediate team visibility
@@ -161,7 +161,7 @@ Best for: Teams that want automatic GitHub integration
 
 **2. No, manual creation**
 ```
-Use /specweave-github:create-issue manually when needed
+Use /sw-github:create-issue manually when needed
 
 Benefits:
 - Create issues only for important increments
@@ -237,7 +237,7 @@ Best for: Migrating from Jira-first workflow to SpecWeave
 
 **4. Manual sync only**
 ```
-Use /specweave-jira:sync command when needed
+Use /sw-jira:sync command when needed
 
 Features:
 - No automatic sync via hooks
@@ -312,7 +312,7 @@ Best for: Migrating from ADO-first workflow to SpecWeave
 
 **4. Manual sync only**
 ```
-Use /specweave-ado:sync command when needed
+Use /sw-ado:sync command when needed
 
 Features:
 - No automatic sync via hooks
@@ -424,7 +424,7 @@ ADO_PAT=xxx
 **Trigger**: Explicit command
 
 **Flow**:
-1. User runs `/specweave-github:sync [increment-id]`
+1. User runs `/sw-github:sync [increment-id]`
 2. Choose direction: pull, push, or bidirectional
 3. Execute sync operation
 4. Report results to user
@@ -470,7 +470,7 @@ GitHub and Jira do NOT sync with each other. SpecWeave is the hub.
 
 **A**:
 1. Set sync direction: **Import-only**
-2. Run: `/specweave-github:import-all`
+2. Run: `/sw-github:import-all`
 3. SpecWeave creates increments from GitHub issues
 4. Review and adjust as needed
 5. Switch to **Bidirectional** when ready
@@ -479,7 +479,7 @@ GitHub and Jira do NOT sync with each other. SpecWeave is the hub.
 
 **A**: Yes! Use manual sync:
 ```bash
-/specweave-github:sync 0042-auth-feature  # Sync specific increment
+/sw-github:sync 0042-auth-feature  # Sync specific increment
 ```
 
 Auto-sync only affects **active** increments (not completed/abandoned).
@@ -488,7 +488,7 @@ Auto-sync only affects **active** increments (not completed/abandoned).
 
 ## Troubleshooting
 
-### Issue: GitHub issue not created after `/specweave:increment`
+### Issue: GitHub issue not created after `/sw:increment`
 
 **Diagnosis**:
 1. Check GitHub CLI: `gh auth status`
@@ -498,7 +498,7 @@ Auto-sync only affects **active** increments (not completed/abandoned).
 **Fix**:
 ```bash
 # Manual creation
-/specweave-github:create-issue 0042-auth-feature
+/sw-github:create-issue 0042-auth-feature
 ```
 
 ### Issue: Jira epic not updating
@@ -512,7 +512,7 @@ Auto-sync only affects **active** increments (not completed/abandoned).
 **Fix**:
 ```bash
 # Manual sync
-/specweave-jira:sync 0042-auth-feature --force
+/sw-jira:sync 0042-auth-feature --force
 ```
 
 ### Issue: Conflict during bidirectional sync
@@ -587,23 +587,23 @@ When experimenting or testing:
 ## Related Slash Commands
 
 ### GitHub
-- `/specweave-github:sync [increment-id]` - Manual sync
-- `/specweave-github:create-issue [increment-id]` - Create issue
-- `/specweave-github:close-issue [increment-id]` - Close issue
-- `/specweave-github:import-all` - Import all GitHub issues
-- `/specweave-github:status [increment-id]` - Check sync status
+- `/sw-github:sync [increment-id]` - Manual sync
+- `/sw-github:create-issue [increment-id]` - Create issue
+- `/sw-github:close-issue [increment-id]` - Close issue
+- `/sw-github:import-all` - Import all GitHub issues
+- `/sw-github:status [increment-id]` - Check sync status
 
 ### Jira
-- `/specweave-jira:sync [increment-id]` - Manual sync
-- `/specweave-jira:create-epic [increment-id]` - Create epic
-- `/specweave-jira:import-all` - Import all Jira epics
-- `/specweave-jira:status [increment-id]` - Check sync status
+- `/sw-jira:sync [increment-id]` - Manual sync
+- `/sw-jira:create-epic [increment-id]` - Create epic
+- `/sw-jira:import-all` - Import all Jira epics
+- `/sw-jira:status [increment-id]` - Check sync status
 
 ### Azure DevOps
-- `/specweave-ado:sync [increment-id]` - Manual sync
-- `/specweave-ado:create-workitem [increment-id]` - Create work item
-- `/specweave-ado:import-all` - Import all ADO work items
-- `/specweave-ado:status [increment-id]` - Check sync status
+- `/sw-ado:sync [increment-id]` - Manual sync
+- `/sw-ado:create-workitem [increment-id]` - Create work item
+- `/sw-ado:import-all` - Import all ADO work items
+- `/sw-ado:status [increment-id]` - Check sync status
 
 ---
 

package/plugins/specweave/skills/{specweave-framework → framework}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-framework
+name: framework
 description: Expert knowledge of SpecWeave framework structure, rules, conventions, and increment lifecycle. Deep understanding of source-of-truth discipline, increment naming, living docs sync. Covers SpecWeave-specific hooks (post-task-completion), and increment discipline. Activates for specweave rules, increment lifecycle, source of truth, increment naming, tasks.md format, spec.md structure, living docs sync, specweave hooks, where do files go, how to use specweave, specweave best practices, specweave conventions.
 allowed-tools: Read, Grep, Glob
 ---
@@ -80,16 +80,16 @@ board: digital-operations    # REQUIRED for 2-level
 ### Increment Lifecycle
 
 ```
-1. Plan    → /specweave:inc "feature-name"
+1. Plan    → /sw:inc "feature-name"
             ↓ PM agent creates spec.md, plan.md, tasks.md, tests.md
 
-2. Execute → /specweave:do
+2. Execute → /sw:do
             ↓ Selects next task, executes, marks complete
 
-3. Validate → /specweave:validate 0001
+3. Validate → /sw:validate 0001
             ↓ Checks spec compliance, test coverage
 
-4. Close   → /specweave:done 0001
+4. Close   → /sw:done 0001
             ↓ Creates COMPLETION-SUMMARY.md, archives
 ```
 
@@ -98,15 +98,15 @@ board: digital-operations    # REQUIRED for 2-level
 **THE IRON RULE**: Cannot start increment N+1 until increment N is DONE!
 
 **Enforcement**:
-- `/specweave:inc` **blocks** if previous increments incomplete
-- Use `/specweave:status` to check all increments
-- Use `/specweave:close` to close incomplete work
+- `/sw:inc` **blocks** if previous increments incomplete
+- Use `/sw:status` to check all increments
+- Use `/sw:close` to close incomplete work
 - `--force` flag for emergencies (logged, should be rare)
 
 **What "DONE" Means**:
 1. All tasks in `tasks.md` marked `[x] Completed`, OR
 2. `COMPLETION-SUMMARY.md` exists with "✅ COMPLETE" status, OR
-3. Explicit closure via `/specweave:close`
+3. Explicit closure via `/sw:close`
 
 **Three Options for Closing**:
 1. **Adjust Scope** - Remove features from spec.md, regenerate tasks
@@ -116,19 +116,19 @@ board: digital-operations    # REQUIRED for 2-level
 **Example**:
 ```bash
 # Check status
-/specweave:status
+/sw:status
 # Shows: 0002 (73% complete), 0003 (50% complete)
 
 # Try to start new increment
-/specweave:inc "0004-new-feature"
+/sw:inc "0004-new-feature"
 # ❌ Blocked! "Close 0002 and 0003 first"
 
 # Close previous work
-/specweave:close
+/sw:close
 # Interactive: Choose force-complete, move tasks, or reduce scope
 
 # Now can proceed
-/specweave:inc "0004-new-feature"
+/sw:inc "0004-new-feature"
 # ✅ Works! Clean slate
 ```
 
@@ -235,7 +235,7 @@ vim src/skills/increment-planner/SKILL.md
 npm run install:skills
 
 # Test (skill activates from .claude/)
-/specweave:inc "test feature"
+/sw:inc "test feature"
 
 # WRONG: Edit installed file
 vim .claude/skills/increment-planner/SKILL.md  # ❌ Gets overwritten!
@@ -345,7 +345,7 @@ Until hooks are fully automated, **YOU MUST**:
 **Core Framework** (always loaded):
 - 8 core skills (increment-planner, spec-generator, context-loader, etc.)
 - 3 core agents (PM, Architect, Tech Lead)
-- 7 core commands (/specweave:inc, /specweave:do, etc.)
+- 7 core commands (/sw:inc, /sw:do, etc.)
 
 **Plugins** (opt-in):
 - `specweave-github` - GitHub integration (issue sync, PR creation)
@@ -372,7 +372,7 @@ Until hooks are fully automated, **YOU MUST**:
    - Scans package.json, directories, env vars
    - Suggests plugins: "Found React. Enable frontend-stack? (Y/n)"
 
-2. **First Increment** (during `/specweave:inc`):
+2. **First Increment** (during `/sw:inc`):
    - Analyzes increment description for keywords
    - Suggests before creating spec: "This needs kubernetes plugin. Enable? (Y/n)"
 
@@ -437,29 +437,29 @@ SpecWeave works with multiple AI coding assistants:
 ## Key Commands
 
 ### Increment Lifecycle
-- `/specweave:inc "feature-name"` - Plan new increment (PM-led process)
-- `/specweave:do` - Execute next task (smart resume)
-- `/specweave:progress` - Show progress, PM gate status, next action
-- `/specweave:validate 0001` - Validate spec, tests, quality
-- `/specweave:done 0001` - Close increment (PM validation)
-- `/specweave:next` - Auto-close if ready, suggest next work
+- `/sw:inc "feature-name"` - Plan new increment (PM-led process)
+- `/sw:do` - Execute next task (smart resume)
+- `/sw:progress` - Show progress, PM gate status, next action
+- `/sw:validate 0001` - Validate spec, tests, quality
+- `/sw:done 0001` - Close increment (PM validation)
+- `/sw:next` - Auto-close if ready, suggest next work
 
 ### Increment Discipline
-- `/specweave:status` - Show all increments and completion status
-- `/specweave:close` - Interactive closure of incomplete increments
+- `/sw:status` - Show all increments and completion status
+- `/sw:close` - Interactive closure of incomplete increments
 
 ### Documentation Sync
-- `/specweave:sync-docs review` - Review strategic docs before implementation
-- `/specweave:sync-docs update` - Update living docs from completed increments
+- `/sw:sync-docs review` - Review strategic docs before implementation
+- `/sw:sync-docs update` - Update living docs from completed increments
 
 ### External Platform Sync
-- `/specweave:sync-github` - Bidirectional GitHub sync
-- `/specweave:sync-jira` - Bidirectional Jira sync
+- `/sw:sync-github` - Bidirectional GitHub sync
+- `/sw:sync-jira` - Bidirectional Jira sync
 
 ## Common Questions
 
 ### Q: Where do I create a new increment?
-**A**: Use `/specweave:inc "####-descriptive-name"`. It creates:
+**A**: Use `/sw:inc "####-descriptive-name"`. It creates:
 ```
 .specweave/increments/####-descriptive-name/
 ├── spec.md
@@ -476,10 +476,10 @@ SpecWeave works with multiple AI coding assistants:
 ```
 
 ### Q: How do I know what tasks are left?
-**A**: Use `/specweave:progress` or read `.specweave/increments/####/tasks.md`
+**A**: Use `/sw:progress` or read `.specweave/increments/####/tasks.md`
 
 ### Q: Can I start a new increment before finishing the current one?
-**A**: NO! (v0.6.0+) The framework **blocks** you. Use `/specweave:status` to check, `/specweave:close` to close.
+**A**: NO! (v0.6.0+) The framework **blocks** you. Use `/sw:status` to check, `/sw:close` to close.
 
 ### Q: Where do I edit skills/agents/commands?
 **A**: Edit in `src/` (source of truth), then run `npm run install:all` to sync to `.claude/`
@@ -510,8 +510,8 @@ I activate when you ask about:
 
 ## When to Use Other Skills/Agents
 
-- **increment-planner** - Planning NEW increments (/specweave:inc)
-- **PM agent** - Leading increment creation (auto-invoked by /specweave:inc)
+- **increment-planner** - Planning NEW increments (/sw:inc)
+- **PM agent** - Leading increment creation (auto-invoked by /sw:inc)
 - **Architect agent** - Designing system architecture
 - **Tech Lead agent** - Code review, best practices
 - **spec-generator** - Creating detailed technical RFCs

package/plugins/specweave/skills/increment-planner/SKILL.md

@@ -694,27 +694,28 @@ Replace placeholders:
 - **`{{BOARD_ID}}`** ← MANDATORY for 2-level (from STEP 0B)
 - `{{PROJECT_FE_ID}}`, `{{PROJECT_BE_ID}}`, `{{PROJECT_SHARED_ID}}` (for multi-repo)
 
-**Key Rules for spec.md:**
-1. **`project:` field MUST be set in YAML frontmatter** (1-level and 2-level)
-2. **`board:` field MUST be set in YAML frontmatter** (2-level only)
-3. **User stories grouped by project** if multi-project (Frontend, Backend, Shared, etc.)
-4. **User story IDs have project prefix**: `US-FE-001`, `US-BE-001` (multi-project)
-5. **AC-IDs have project prefix**: `AC-FE-US1-01`, `AC-BE-US1-01` (multi-project)
-
-**VALIDATION (spec.md frontmatter):**
-```yaml
-# 1-level structure (REQUIRED):
-project: digital-operations    # ← MUST be set
+**Key Rules for spec.md (ADR-0140: v0.35.0+):**
+1. **`project:` field REMOVED from YAML frontmatter** - now resolved from per-US fields
+2. **`board:` field REMOVED from YAML frontmatter** (2-level) - now in per-US fields
+3. **Each User Story MUST have `**Project**:` field** - source of truth for project
+4. **Each User Story (2-level) MUST have `**Board**:` field** - source of truth for board
+5. **User story IDs have project prefix**: `US-FE-001`, `US-BE-001` (multi-project)
+6. **AC-IDs have project prefix**: `AC-FE-US1-01`, `AC-BE-US1-01` (multi-project)
+
+**VALIDATION (per-US fields - v0.35.0+):**
+```markdown
+### US-001: Feature Name
+**Project**: digital-operations    # ← REQUIRED (resolved from config)
 
-# 2-level structure (BOTH REQUIRED):
-project: acme-corp             # ← MUST be set
-board: digital-operations      # ← MUST be set
+### US-001: Feature Name (2-level)
+**Project**: acme-corp             # ← REQUIRED
+**Board**: digital-operations      # ← REQUIRED for 2-level
 ```
 
 **⚠️ FORBIDDEN:**
-- Creating spec.md with `project: {{PROJECT_ID}}` (unresolved placeholder)
-- Creating spec.md for 2-level with `board: {{BOARD_ID}}` (unresolved placeholder)
-- Leaving project/board fields empty or undefined
+- User stories without `**Project**:` field
+- User stories (2-level) without `**Board**:` field
+- Using unresolved placeholders like `{{PROJECT_ID}}`
 
 ### STEP 5: Create plan.md Template
 
@@ -846,7 +847,7 @@ This step uses the existing sync infrastructure to:
 **Run the sync-specs command:**
 
 ```bash
-/specweave:sync-specs {increment-id}
+/sw:sync-specs {increment-id}
 ```
 
 **Expected output:**
@@ -874,7 +875,7 @@ If `canUpsertInternalItems: false` in config:
 External tool sync failures are NON-BLOCKING:
 ```
 ⚠️ External sync failed: Rate limit exceeded
-💡 Run /specweave:sync-specs {increment-id} to retry
+💡 Run /sw:sync-specs {increment-id} to retry
 ```
 
 **Output after sync:**
@@ -884,8 +885,8 @@ External tool sync failures are NON-BLOCKING:
 
 Next steps:
 1. Review the increment plan and docs
-2. Start implementation: /specweave:do {increment-id}
-3. Monitor status: /specweave:status {increment-id}
+2. Start implementation: /sw:do {increment-id}
+3. Monitor status: /sw:status {increment-id}
 ```
 
 ---
@@ -1042,17 +1043,17 @@ node plugins/specweave/skills/increment-planner/scripts/generate-short-name.js "
 
 **GitHub Issues**: After increment creation, optionally sync to GitHub:
 ```bash
-/specweave-github:create-issue 0021
+/sw-github:create-issue 0021
 ```
 
 **Jira Epics**: Sync to Jira:
 ```bash
-/specweave-jira:sync 0021
+/sw-jira:sync 0021
 ```
 
 **Azure DevOps**: Sync to ADO work items:
 ```bash
-/specweave-ado:create-workitem 0021
+/sw-ado:create-workitem 0021
 ```
 
 ---

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