specweave 0.33.5 → 0.34.0

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

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