specweave 0.33.4 → 0.33.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specweave",
-  "version": "0.33.4",
+  "version": "0.33.6",
   "description": "Spec-driven development framework for Claude Code. AI-native workflow with living documentation, intelligent agents, and multilingual support (9 languages). Enterprise-grade traceability with permanent specs and temporary increments.",
   "type": "module",
   "main": "dist/index.js",
@@ -88,6 +88,7 @@
     "@inquirer/prompts": "^8.0.1",
     "@octokit/rest": "^22.0.1",
     "@types/handlebars": "^4.0.40",
+    "@types/prompts": "^2.4.9",
     "axios": "^1.13.2",
     "chalk": "^5.3.0",
     "commander": "^14.0.2",
@@ -97,6 +98,7 @@
     "js-yaml": "^4.1.0",
     "open": "^11.0.0",
     "ora": "^9.0.0",
+    "prompts": "^2.4.2",
     "uuid": "^13.0.0",
     "yaml": "^2.3.4",
     "zod": "^4.1.13"

package/plugins/PLUGINS-INDEX.md

@@ -2,7 +2,7 @@
 
 **Purpose**: Lightweight plugin manifest for progressive disclosure. Load plugin content only when triggers match.
 
-**Total Plugins**: 26 | **Last Updated**: 2025-12-04
+**Total Plugins**: 25 | **Last Updated**: 2025-12-11
 
 ---
 
@@ -87,7 +87,6 @@
 
 | Plugin | Triggers | Description |
 |--------|----------|-------------|
-| **specweave-core** | core utilities, shared, common | Core shared utilities |
 | **specweave-plugin-dev** | create plugin, plugin development | Plugin development guide |
 | **specweave-tooling** | tooling, skill create, agent create | SpecWeave tooling |
 

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

@@ -1,5 +1,5 @@
 {
-  "name": "specweave",
+  "name": "sw",
   "description": "SpecWeave framework. Provides increment planning (PM, Architect, Tech Lead agents), specification generation, TDD workflow, living docs sync, and brownfield support. Essential for all SpecWeave projects.",
   "version": "0.25.0",
   "author": {

package/plugins/specweave/COMMANDS.md

@@ -4,20 +4,20 @@ All SpecWeave commands are namespaced for brownfield safety and follow a consist
 
 ## ⚠️ CRITICAL: No Shortcuts Allowed
 
-**IMPORTANT**: SpecWeave commands MUST be invoked with the `/specweave:*` namespace prefix.
+**IMPORTANT**: SpecWeave commands MUST be invoked with the `/sw:*` namespace prefix.
 
 **Why?** Shortcuts like `/inc`, `/do`, `/pause`, `/resume` conflict with Claude Code's native commands and break functionality.
 
-**Always use**: `/specweave:increment`, `/specweave:do`, `/specweave:resume`, etc.
+**Always use**: `/sw:increment`, `/sw:do`, `/sw:resume`, etc.
 
 ## Command Naming Convention
 
-**All command files**: `specweave-{command-name}.md`
-**YAML name field**: `{command-name}` (without `specweave-` prefix)
-**Invocation**: `/specweave:{command-name}` (namespace prefix required)
+**All command files**: `{command-name}.md` (simplified in v0.34.0)
+**YAML name field**: `{command-name}`
+**Invocation**: `/sw:{command-name}` (namespace prefix required)
 
 ### Example:
-- **File**: `specweave-increment.md`
+- **File**: `increment.md`
 - **YAML**:
   ```yaml
   ---
@@ -25,51 +25,51 @@ All SpecWeave commands are namespaced for brownfield safety and follow a consist
   description: Plan new Product Increment
   ---
   ```
-- **Usage**: `/specweave:increment` (ONLY form, no shortcuts)
+- **Usage**: `/sw:increment` (ONLY form, no shortcuts)
 
 ## All Available Commands
 
 ### Core Lifecycle (7 commands)
-1. `specweave-increment.md` - Create increment → `/specweave:increment`
-2. `specweave-do.md` - Execute tasks → `/specweave:do`
-3. `specweave-done.md` - Close increment → `/specweave:done`
-4. `specweave-next.md` - Smart transition → `/specweave:next`
-5. `specweave-progress.md` - Current progress → `/specweave:progress`
-6. `specweave-validate.md` - Validate quality → `/specweave:validate`
-7. `specweave-sync-docs.md` - Sync documentation → `/specweave:sync-docs`
+1. `increment.md` - Create increment → `/sw:increment`
+2. `do.md` - Execute tasks → `/sw:do`
+3. `done.md` - Close increment → `/sw:done`
+4. `next.md` - Smart transition → `/sw:next`
+5. `progress.md` - Current progress → `/sw:progress`
+6. `validate.md` - Validate quality → `/sw:validate`
+7. `sync-docs.md` - Sync documentation → `/sw:sync-docs`
 
 ### Status & Reporting (4 commands)
-8. `specweave-status.md` - All increments overview → `/specweave:status`
-9. `specweave-costs.md` - AI cost dashboard → `/specweave:costs`
-10. `specweave-update-scope.md` - Update completion report → `/specweave:update-scope`
-11. `specweave-qa.md` - Quality assessment → `/specweave:qa`
+8. `status.md` - All increments overview → `/sw:status`
+9. `costs.md` - AI cost dashboard → `/sw:costs`
+10. `update-scope.md` - Update completion report → `/sw:update-scope`
+11. `qa.md` - Quality assessment → `/sw:qa`
 
 ### State Management (3 commands)
-12. `specweave-pause.md` - Pause increment → `/specweave:pause`
-13. `specweave-resume.md` - Resume increment → `/specweave:resume`
-14. `specweave-abandon.md` - Abandon increment → `/specweave:abandon`
+12. `pause.md` - Pause increment → `/sw:pause`
+13. `resume.md` - Resume increment → `/sw:resume`
+14. `abandon.md` - Abandon increment → `/sw:abandon`
 
 ### Testing & Quality (2 commands)
-15. `specweave-check-tests.md` - Validate test coverage → `/specweave:check-tests`
-16. `specweave-sync-tasks.md` - Sync tasks with GitHub → `/specweave:sync-tasks`
+15. `check-tests.md` - Validate test coverage → `/sw:check-tests`
+16. `sync-tasks.md` - Sync tasks with GitHub → `/sw:sync-tasks`
 
 ### TDD Workflow (4 commands)
-17. `specweave-tdd-red.md` - Write failing tests → `/specweave:tdd-red`
-18. `specweave-tdd-green.md` - Make tests pass → `/specweave:tdd-green`
-19. `specweave-tdd-refactor.md` - Refactor code → `/specweave:tdd-refactor`
-20. `specweave-tdd-cycle.md` - Full TDD cycle → `/specweave:tdd-cycle`
+17. `tdd-red.md` - Write failing tests → `/sw:tdd-red`
+18. `tdd-green.md` - Make tests pass → `/sw:tdd-green`
+19. `tdd-refactor.md` - Refactor code → `/sw:tdd-refactor`
+20. `tdd-cycle.md` - Full TDD cycle → `/sw:tdd-cycle`
 
 ### Archiving & Cleanup (6 commands)
-21. `specweave-archive.md` - Archive increments → `/specweave:archive`
-22. `specweave-restore.md` - Restore from archive → `/specweave:restore`
-23. `specweave-archive-features.md` - Archive features/epics → `/specweave:archive-features`
-24. `specweave-restore-feature.md` - Restore features/epics → `/specweave:restore-feature`
-25. `specweave-fix-duplicates.md` - Resolve duplicate increments → `/specweave:fix-duplicates`
-26. `specweave-backlog.md` - Move to backlog → `/specweave:backlog`
+21. `archive.md` - Archive increments → `/sw:archive`
+22. `restore.md` - Restore from archive → `/sw:restore`
+23. `archive-features.md` - Archive features/epics → `/sw:archive-features`
+24. `restore-feature.md` - Restore features/epics → `/sw:restore-feature`
+25. `fix-duplicates.md` - Resolve duplicate increments → `/sw:fix-duplicates`
+26. `backlog.md` - Move to backlog → `/sw:backlog`
 
 ### Utilities (2 commands)
-27. `specweave-translate.md` - Batch translation → `/specweave:translate`
-28. `specweave.md` - Master router → `/specweave`
+27. `translate.md` - Batch translation → `/sw:translate`
+28. `sw.md` - Master router → `/sw`
 
 **Total**: 28 commands (6 new archiving/cleanup commands added in v0.18.3)
 
@@ -84,34 +84,34 @@ All SpecWeave commands are namespaced for brownfield safety and follow a consist
 ## Removed/Deprecated Commands
 
 **Duplicates removed** (v0.7.0 refactoring):
-- ❌ `inc.md` → Use `/specweave:increment`
-- ❌ `status.md` → Use `/specweave:status`
-- ❌ `pause.md` → Use `/specweave:pause`
-- ❌ `resume.md` → Use `/specweave:resume`
-- ❌ `abandon.md` → Use `/specweave:abandon`
+- ❌ `inc.md` → Use `/sw:increment`
+- ❌ `status.md` → Use `/sw:status`
+- ❌ `pause.md` → Use `/sw:pause`
+- ❌ `resume.md` → Use `/sw:resume`
+- ❌ `abandon.md` → Use `/sw:abandon`
 
 **Deprecated commands**:
-- ❌ `validate-coverage.md` → Use `/specweave:check-tests` (NEW format)
-- ❌ `specweave-validate-coverage.md` → Use `/specweave:check-tests`
+- ❌ `validate-coverage.md` → Use `/sw:check-tests` (NEW format)
+- ❌ `specweave-validate-coverage.md` → Use `/sw:check-tests`
 
 **Redundant commands**:
-- ❌ `list-increments.md` → Use `/specweave:status` (same functionality)
+- ❌ `list-increments.md` → Use `/sw:status` (same functionality)
 
 ## Brownfield Safety
 
 All commands are namespaced to prevent collisions with existing project commands:
-- ✅ **Namespace form**: `/specweave:increment` (ONLY way, always safe)
+- ✅ **Namespace form**: `/sw:increment` (ONLY way, always safe)
 - ❌ **No shortcuts**: Do NOT use `/inc`, `/do`, `/pause`, `/resume` etc.
 
 ## Command Usage Philosophy
 
 **Correct usage** (namespace prefix required):
 ```bash
-/specweave:increment "feature"   # Create increment
-/specweave:do                    # Execute tasks
-/specweave:status                # Check progress
-/specweave:qa 0007               # Quality check
-/specweave:done 0007             # Close increment
+/sw:increment "feature"   # Create increment
+/sw:do                    # Execute tasks
+/sw:status                # Check progress
+/sw:qa 0007               # Quality check
+/sw:done 0007             # Close increment
 ```
 
 **Incorrect usage** (DO NOT USE):

package/plugins/specweave/agents/pm/AGENT.md

@@ -237,14 +237,14 @@ These guides contain:
 An increment is DONE if **ONE** of:
 1. All tasks in `tasks.md` marked `[x] Completed`
 2. `COMPLETION-SUMMARY.md` exists with "✅ COMPLETE" status
-3. Explicit closure via `/specweave:close`
+3. Explicit closure via `/sw:close`
 
 ### Your Responsibility
 
 As PM Agent, you are the **gatekeeper**. You MUST:
 - ✅ Check for incomplete increments BEFORE planning
 - ✅ Block if any found (no exceptions!)
-- ✅ Direct user to `/specweave:close`
+- ✅ Direct user to `/sw:close`
 - ❌ NEVER plan new increment with incomplete previous work
 
 **This is NOT optional. This is framework integrity.**
@@ -272,17 +272,17 @@ I don't embed all implementation details - I rely on **specialized skills that a
 Skills auto-load based on keywords in user requests:
 
 ```
-User: "/specweave:increment 'auth' with GitHub sync"
+User: "/sw:increment 'auth' with GitHub sync"
   ↓
 PM Agent (26KB) + external-sync-wizard skill (20KB) = 46KB
 (vs 64KB if everything embedded)
 
-User: "/specweave:increment 'add dark mode'"
+User: "/sw:increment 'add dark mode'"
   ↓
 PM Agent (26KB) only = 26KB
 (60% context reduction!)
 
-User: "/specweave:done 0042"
+User: "/sw:done 0042"
   ↓
 PM Agent (26KB) + pm-closure-validation skill (18KB) = 44KB
 ```
@@ -375,7 +375,7 @@ if (shouldSuggestLivingDocs) {
   console.log('  ✅ Increment specs reference it (avoid duplication)');
   console.log('');
   console.log('Location: .specweave/docs/internal/specs/{project}/FS-####/FEATURE.md');
-  console.log('⚠️  CRITICAL: Living docs created via /specweave:sync-docs update!');
+  console.log('⚠️  CRITICAL: Living docs created via /sw:sync-docs update!');
   console.log('');
   console.log('💡 See FAQ: https://spec-weave.com/docs/faq#do-i-need-both-for-every-feature');
   console.log('');
@@ -887,7 +887,7 @@ The PM Agent acts as your AI Product Manager, helping you:
 
 **⚠️ CRITICAL (v5.0.0+)**: The `_features/` folder is OBSOLETE! Features ALWAYS go in `{project}/FS-XXX/`.
 
-**CRITICAL**: Living docs are created via `/specweave:sync-docs update` - NOT manually created!
+**CRITICAL**: Living docs are created via `/sw:sync-docs update` - NOT manually created!
 
 **Purpose**: Complete, detailed requirements specification - PERMANENT source of truth
 
@@ -1358,7 +1358,7 @@ Based on your answers, I'll calculate RICE scores and create a prioritized roadm
 
 **MANDATORY STEP**: After creating increment files, you MUST ACTUALLY EXECUTE metadata.json validation using Read and Write tools.
 
-**NOTE (v0.24.5+)**: The `increment-planner` skill now has explicit Step 11 for metadata.json creation. This validation is a **safety net** if the skill is bypassed or if you're invoked directly via `/specweave:increment`.
+**NOTE (v0.24.5+)**: The `increment-planner` skill now has explicit Step 11 for metadata.json creation. This validation is a **safety net** if the skill is bypassed or if you're invoked directly via `/sw:increment`.
 
 ### Why This Matters
 
@@ -1366,7 +1366,7 @@ Without metadata.json:
 - ❌ Status line shows nothing (no active increment tracking)
 - ❌ WIP limits don't work (can't count active increments)
 - ❌ External sync breaks (no GitHub/JIRA/ADO links)
-- ❌ `/specweave:status`, `/pause`, `/resume` commands fail
+- ❌ `/sw:status`, `/pause`, `/resume` commands fail
 
 ### Validation Workflow (EXECUTE WITH TOOLS!)
 
@@ -1409,7 +1409,7 @@ After creating metadata.json, output:
    This indicates the post-increment-planning hook may have failed.
    ✅ Created minimal metadata.json
    ⚠️  Note: No GitHub issue linked.
-   💡 Run /specweave-github:create-issue {incrementId} to create one manually.
+   💡 Run /sw-github:create-issue {incrementId} to create one manually.
 ```
 
 ### Example Execution (ACTUAL TOOL USAGE)
@@ -1447,7 +1447,7 @@ If missing, it would create minimal metadata...
 **Example workflow**:
 
 ```markdown
-User: /specweave:increment "Add user authentication"
+User: /sw:increment "Add user authentication"
 
 PM Agent workflow:
 1. Validate no incomplete increments ✅
@@ -1566,7 +1566,7 @@ if (!fs.existsSync(metadataPath)) {
   fs.writeFileSync(metadataPath, JSON.stringify(metadata, null, 2), 'utf-8');
   console.log(`   ✅ Created minimal metadata.json`);
   console.log(`   ⚠️  Note: No GitHub issue linked.`);
-  console.log(`   💡 Run /specweave-github:create-issue ${incrementId} to create one manually.`);
+  console.log(`   💡 Run /sw-github:create-issue ${incrementId} to create one manually.`);
 } else {
   console.log(`✅ Increment validation passed - metadata.json exists`);
 
@@ -1594,7 +1594,7 @@ if (!fs.existsSync(metadataPath)) {
 **Example workflow**:
 
 ```markdown
-User: /specweave:increment "Add user authentication"
+User: /sw:increment "Add user authentication"
 
 PM Agent workflow:
 1. Validate no incomplete increments ✅
@@ -1618,7 +1618,7 @@ PM Agent workflow:
    Creating minimal metadata as fallback...
    ✅ Created minimal metadata.json
    ⚠️  Note: No GitHub issue linked.
-   💡 Run /specweave-github:create-issue 0023-release-management to create one manually.
+   💡 Run /sw-github:create-issue 0023-release-management to create one manually.
 ```
 
 **Scenario 2: Hook succeeded**
@@ -1645,7 +1645,7 @@ PM Agent workflow:
 
 **Test Case 1: Normal flow (hook succeeds)**
 ```bash
-/specweave:increment "Test feature"
+/sw:increment "Test feature"
 # Expected: metadata.json created by hook
 # Validation: Passes with GitHub issue link
 ```
@@ -1653,7 +1653,7 @@ PM Agent workflow:
 **Test Case 2: Hook fails (no gh CLI)**
 ```bash
 # Remove gh CLI: brew uninstall gh
-/specweave:increment "Test feature"
+/sw:increment "Test feature"
 # Expected: metadata.json NOT created by hook
 # Validation: Creates minimal metadata, warns user
 ```
@@ -1661,7 +1661,7 @@ PM Agent workflow:
 **Test Case 3: GitHub disabled**
 ```bash
 # Set autoCreateIssue: false in config
-/specweave:increment "Test feature"
+/sw:increment "Test feature"
 # Expected: metadata.json created by hook (no GitHub section)
 # Validation: Passes with info message
 ```
@@ -1834,7 +1834,7 @@ Example:
 
 **Why AC-IDs Matter**:
 - ✅ Traceability: AC → Task → Test (bidirectional linking)
-- ✅ Test Coverage: /specweave:check-tests validates all AC-IDs are tested
+- ✅ Test Coverage: /sw:check-tests validates all AC-IDs are tested
 - ✅ Quality: Ensures no acceptance criteria are missed
 - ✅ Communication: Clear reference in discussions ("AC-US1-01 is failing")
 

package/plugins/specweave/agents/test-aware-planner/AGENT.md

@@ -440,7 +440,7 @@ Before finalizing tasks.md:
 - ARCHITECTURE-PIVOT.md (rationale for eliminating tests.md)
 - plan.md (technical architecture)
 - spec.md (user stories and AC-IDs)
-- /specweave:check-tests command (validates test coverage)
+- /sw:check-tests command (validates test coverage)
 
 ---
 
@@ -971,13 +971,13 @@ Files created:
 
 Next steps:
 1. Review tasks.md for completeness
-2. Validate AC-ID coverage: /specweave:validate {increment-id} --acs
-3. Begin implementation: /specweave:do {increment-id}
+2. Validate AC-ID coverage: /sw:validate {increment-id} --acs
+3. Begin implementation: /sw:do {increment-id}
 ```
 
-**Step 5.2: Integration with /specweave:check-tests**
+**Step 5.2: Integration with /sw:check-tests**
 
-After tasks are implemented, the `/specweave:check-tests` command will validate:
+After tasks are implemented, the `/sw:check-tests` command will validate:
 - Which tasks have tests implemented
 - Whether tests pass
 - Whether coverage targets are met
@@ -1188,7 +1188,7 @@ diff tasks.md.bak tasks.md
 2. **Architect Agent** → Creates `plan.md` (technical architecture + test strategy)
 3. **Test-Aware Planner** (THIS AGENT) → Creates `tasks.md` (tasks with embedded tests)
 4. **Tech Lead Agent** → Executes tasks from `tasks.md`
-5. **/specweave:check-tests** → Validates test coverage and AC-ID mapping
+5. **/sw:check-tests** → Validates test coverage and AC-ID mapping
 
 **Data Flow:**
 
@@ -1197,7 +1197,7 @@ spec.md (AC-IDs) ──┐
                     ├─→ test-aware-planner → tasks.md (tasks + tests)
 plan.md (arch)  ──┘
 
-tasks.md → Tech Lead Agent → Implementation → /specweave:check-tests → Coverage Report
+tasks.md → Tech Lead Agent → Implementation → /sw:check-tests → Coverage Report
 ```
 
 ---

package/plugins/specweave/agents/translator/AGENT.md

@@ -266,7 +266,7 @@ Quality checks:
 ### ⏸️ **Keep in English**:
 - Framework terms: increment, spec.md, plan.md, tasks.md, COMPLETION-SUMMARY.md
 - File paths: .specweave/, src/, .claude/
-- Commands: /specweave:inc, /specweave:do, /specweave:progress
+- Commands: /sw:inc, /sw:do, /sw:progress
 - Technical terms: TypeScript, npm, git, API, CLI, REST, JSON, HTTP
 - SpecWeave keywords: living docs, context-manifest.yaml, PM gate
 - Code identifiers: function names, class names, variable names
@@ -321,7 +321,7 @@ Discovered Files:
 Total: 39 files
 
 Estimated Time: 30-45 minutes
-Framework Terms Preserved: increment, spec.md, plan.md, tasks.md, /specweave:*
+Framework Terms Preserved: increment, spec.md, plan.md, tasks.md, /sw:*
 
 Proceed with translation? (Y/n)
 ```

package/plugins/specweave/commands/{specweave-abandon.md → abandon.md}

@@ -1,12 +1,12 @@
 ---
-name: specweave:abandon
+name: sw:abandon
 description: Abandon an incomplete increment (requirements changed, obsolete)
-usage: /specweave:abandon <increment-id> --reason="<reason>"
+usage: /sw:abandon <increment-id> --reason="<reason>"
 ---
 
 # Abandon Increment Command
 
-**Usage**: `/specweave:abandon <increment-id> --reason="<reason>"`
+**Usage**: `/sw:abandon <increment-id> --reason="<reason>"`
 
 ⚠️  **THIS ACTION MOVES THE INCREMENT TO `_archive/` FOLDER**
 
@@ -42,7 +42,7 @@ Abandon an increment when:
 
 ### Abandon with reason
 ```bash
-/specweave:abandon 0008 --reason="Requirements changed - feature no longer needed"
+/sw:abandon 0008 --reason="Requirements changed - feature no longer needed"
 
 ⚠️  This will move increment 0008 to _archive/
    Reason: Requirements changed - feature no longer needed
@@ -59,7 +59,7 @@ Continue? [y/N]: y
 
 ### Abandon without reason (prompts)
 ```bash
-/specweave:abandon 0009
+/sw:abandon 0009
 
 ❓ Why are you abandoning this increment?
    1. Requirements changed
@@ -85,7 +85,7 @@ Continue? [y/N]: y
 
 ### Cannot Abandon Completed
 ```bash
-/specweave:abandon 0005
+/sw:abandon 0005
 
 ❌ Cannot abandon increment 0005
    Status: completed
@@ -96,7 +96,7 @@ Continue? [y/N]: y
 
 ### Already Abandoned
 ```bash
-/specweave:abandon 0008
+/sw:abandon 0008
 
 ⚠️  Increment 0008 is already abandoned
    Location: .specweave/increments/_abandoned/0008-old-feature/
@@ -107,15 +107,15 @@ No action needed.
 
 ### Increment Not Found
 ```bash
-/specweave:abandon 9999
+/sw:abandon 9999
 
 ❌ Increment not found: 9999
-💡 Check available increments: /specweave:status
+💡 Check available increments: /sw:status
 ```
 
 ### Cancel Abandonment
 ```bash
-/specweave:abandon 0008 --reason="Not needed"
+/sw:abandon 0008 --reason="Not needed"
 
 ⚠️  This will move increment 0008 to _archive/
    Reason: Not needed
@@ -211,7 +211,7 @@ mv .specweave/increments/_archive/0008-feature \
    .specweave/increments/0008-feature
 
 # 2. Resume via command
-/specweave:resume 0008
+/sw:resume 0008
 
 ✅ Increment 0008 resumed
 ⚠️  Note: Was abandoned 10 days ago
@@ -223,10 +223,10 @@ mv .specweave/increments/_archive/0008-feature \
 
 ## Related Commands
 
-- `/specweave:pause <id>` - Pause increment (temporary, can resume)
-- `/specweave:resume <id>` - Resume paused or abandoned increment
-- `/specweave:status` - Show all increments (including abandoned count)
-- `/specweave:status --abandoned` - Show only abandoned increments
+- `/sw:pause <id>` - Pause increment (temporary, can resume)
+- `/sw:resume <id>` - Resume paused or abandoned increment
+- `/sw:status` - Show all increments (including abandoned count)
+- `/sw:status --abandoned` - Show only abandoned increments
 
 ---
 
@@ -252,12 +252,12 @@ Experiments (--type=experiment) auto-abandon after **14 days** of inactivity:
 
 ```bash
 # Create experiment
-/specweave:inc "Try GraphQL" --type=experiment
+/sw:inc "Try GraphQL" --type=experiment
 
 # ... 15 days pass with no activity ...
 
 # Automatic abandonment
-/specweave:status
+/sw:status
 
 📊 Auto-Abandoned (1):
   🧪 0010-graphql-experiment [experiment]
@@ -266,7 +266,7 @@ Experiments (--type=experiment) auto-abandon after **14 days** of inactivity:
      Last activity: 15 days ago
 
 💡 Experiments auto-abandon after 14 days of inactivity
-   To prevent: Update lastActivity via /specweave:do or manual touch
+   To prevent: Update lastActivity via /sw:do or manual touch
 ```
 
 ---
@@ -276,7 +276,7 @@ Experiments (--type=experiment) auto-abandon after **14 days** of inactivity:
 View abandonment statistics:
 
 ```bash
-/specweave:status
+/sw:status
 
 ✅ Completed (4):
   0001-core-framework
@@ -310,7 +310,7 @@ Abandoned work is valuable!
 
 ---
 
-**Command**: `/specweave:abandon`
+**Command**: `/sw:abandon`
 **Plugin**: specweave (core)
 **Version**: v0.7.0+
 **Part of**: Increment 0007 - Smart Status Management

package/plugins/specweave/commands/{specweave-analyze-standards.sh → analyze-standards.sh}

@@ -2,7 +2,7 @@
 # ---
 # name: specweave-analyze-standards
 # description: Analyze and document coding standards from codebase. Detects naming conventions, import patterns, type usage, and anti-patterns. Generates evidence-based standards documentation with confidence levels. Supports full analysis, drift detection, and standards updates.
-# usage: /specweave:analyze-standards [--drift] [--update] [--verbose]
+# usage: /sw:analyze-standards [--drift] [--update] [--verbose]
 # ---
 
 set -e
@@ -40,7 +40,7 @@ while [[ $# -gt 0 ]]; do
       ;;
     *)
       echo "❌ Unknown option: $1"
-      echo "Usage: /specweave:analyze-standards [--drift] [--update] [--verbose]"
+      echo "Usage: /sw:analyze-standards [--drift] [--update] [--verbose]"
       exit 1
       ;;
   esac
@@ -148,7 +148,7 @@ AGENT_PROMPT
       echo "❌ Error: No coding standards found at:"
       echo "   $GOVERNANCE_DIR/coding-standards.md"
       echo ""
-      echo "💡 Tip: Run /specweave:analyze-standards first to generate baseline standards"
+      echo "💡 Tip: Run /sw:analyze-standards first to generate baseline standards"
       exit 1
     fi
 
@@ -299,7 +299,7 @@ case $MODE in
   full)
     echo "   1. Review the analysis report"
     echo "   2. Fix critical issues (hardcoded secrets, etc.)"
-    echo "   3. Run /specweave:analyze-standards --update to formalize"
+    echo "   3. Run /sw:analyze-standards --update to formalize"
     ;;
   drift)
     echo "   1. Review drift report"

package/plugins/specweave/commands/{specweave-archive-features.md → archive-features.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:archive-features
+name: sw:archive-features
 description: Archive features and epics when all related increments are archived
 ---
 
@@ -10,7 +10,7 @@ Archive features and epics based on their increment archive status. Features are
 ## Usage
 
 ```bash
-/specweave:archive-features [options]
+/sw:archive-features [options]
 ```
 
 ## Options
@@ -25,16 +25,16 @@ Archive features and epics based on their increment archive status. Features are
 
 ```bash
 # Preview what would be archived
-/specweave:archive-features --dry-run
+/sw:archive-features --dry-run
 
 # Archive features and update all links
-/specweave:archive-features
+/sw:archive-features
 
 # Archive including orphaned features
-/specweave:archive-features --orphaned
+/sw:archive-features --orphaned
 
 # Archive with custom reason for audit trail (AC-US13-07)
-/specweave:archive-features --reason="Obsolete after product pivot"
+/sw:archive-features --reason="Obsolete after product pivot"
 ```
 
 ## Archive Rules
@@ -67,7 +67,7 @@ Archive features and epics based on their increment archive status. Features are
 
 - Archives are LOCAL ONLY (not synced to GitHub/JIRA/ADO)
 - All links are automatically updated to point to archive locations
-- Use `/specweave:restore-feature FS-001` to restore from archive
+- Use `/sw:restore-feature FS-001` to restore from archive
 
 ## Implementation