specweave 0.33.4 → 0.33.6

package/plugins/specweave-ado/commands/status.md

@@ -1,11 +1,11 @@
 ---
-name: specweave-ado:status
+name: sw-ado:status
 description: Check Azure DevOps sync status for increment
 ---
 
 # ADO Status Command
 
-**Usage**: `/specweave-ado:status <increment-id>`
+**Usage**: `/sw-ado:status <increment-id>`
 
 **Purpose**: Display ADO sync status and work item details
 
@@ -58,8 +58,8 @@ Next Sync: Automatic on task completion
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:pull` | Pull changes from ADO |
-| `/specweave-ado:push` | Push progress to ADO |
-| `/specweave-ado:sync` | Two-way sync |
-| `/specweave-ado:create` | Create ADO work item |
-| `/specweave-ado:close` | Close work item |
+| `/sw-ado:pull` | Pull changes from ADO |
+| `/sw-ado:push` | Push progress to ADO |
+| `/sw-ado:sync` | Two-way sync |
+| `/sw-ado:create` | Create ADO work item |
+| `/sw-ado:close` | Close work item |

package/plugins/specweave-ado/commands/sync.md

@@ -1,11 +1,11 @@
 ---
-name: specweave-ado:sync
+name: sw-ado:sync
 description: Two-way sync between SpecWeave increment and Azure DevOps work item (push & pull by default)
 ---
 
 # Sync ADO Work Item Command
 
-**Usage**: `/specweave-ado:sync <increment-id> [options]`
+**Usage**: `/sw-ado:sync <increment-id> [options]`
 
 **Purpose**: Two-way synchronization between SpecWeave increment and Azure DevOps work item
 
@@ -24,13 +24,13 @@ description: Two-way sync between SpecWeave increment and Azure DevOps work item
 
 ```bash
 # Two-way sync (default - both directions)
-/specweave-ado:sync 0005
+/sw-ado:sync 0005
 
 # Push only (one-way to ADO)
-/specweave-ado:sync 0005 --direction to-ado
+/sw-ado:sync 0005 --direction to-ado
 
 # Pull only (one-way from ADO)
-/specweave-ado:sync 0005 --direction from-ado
+/sw-ado:sync 0005 --direction from-ado
 ```
 
 ---
@@ -74,7 +74,7 @@ Cannot push changes to ADO (sync.settings.canUpdateExternalItems = false).
 
 Options:
 1. Enable writes: Set canUpdateExternalItems to true in config.json
-2. Pull-only mode: /specweave-ado:sync ${incrementId} --direction from-ado
+2. Pull-only mode: /sw-ado:sync ${incrementId} --direction from-ado
 `);
     return;
   }
@@ -200,7 +200,7 @@ This allows:
 ### Two-way Sync (Default)
 
 ```
-User: /specweave-ado:sync 0005-payment-integration
+User: /sw-ado:sync 0005-payment-integration
 
 Claude:
 Checking permissions...
@@ -232,7 +232,7 @@ Work Item: https://dev.azure.com/acme-corp/My%20Project/_workitems/edit/12345
 ### Permission Denied
 
 ```
-User: /specweave-ado:sync 0005 --direction to-ado
+User: /sw-ado:sync 0005 --direction to-ado
 
 Claude:
 Checking permissions...
@@ -244,7 +244,7 @@ Cannot push changes to ADO.
 
 Options:
 1. Enable writes: Set sync.settings.canUpdateExternalItems = true
-2. Pull-only: /specweave-ado:sync 0005 --direction from-ado
+2. Pull-only: /sw-ado:sync 0005 --direction from-ado
 ```
 
 ---
@@ -255,10 +255,10 @@ For most use cases, use the git-style commands:
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:pull` | Pull changes from ADO (read-only) |
-| `/specweave-ado:push` | Push progress to ADO |
+| `/sw-ado:pull` | Pull changes from ADO (read-only) |
+| `/sw-ado:push` | Push progress to ADO |
 
-Use `/specweave-ado:sync` when you need explicit two-way sync with options.
+Use `/sw-ado:sync` when you need explicit two-way sync with options.
 
 ---
 
@@ -326,8 +326,8 @@ AZURE_DEVOPS_PAT=your-personal-access-token
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-ado:pull` | Pull from ADO (git-style) |
-| `/specweave-ado:push` | Push to ADO (git-style) |
-| `/specweave-ado:create` | Create new ADO work item |
-| `/specweave-ado:status` | Check sync status |
-| `/specweave-ado:close` | Close work item when complete |
+| `/sw-ado:pull` | Pull from ADO (git-style) |
+| `/sw-ado:push` | Push to ADO (git-style) |
+| `/sw-ado:create` | Create new ADO work item |
+| `/sw-ado:status` | Check sync status |
+| `/sw-ado:close` | Close work item when complete |

package/plugins/specweave-ado/hooks/post-living-docs-update.sh

@@ -8,8 +8,8 @@
 # CRITICAL: External tool status ALWAYS wins in conflicts!
 #
 # Triggers:
-# 1. After /specweave:done (increment completion)
-# 2. After /specweave:sync-docs update
+# 1. After /sw:done (increment completion)
+# 2. After /sw:sync-docs update
 # 3. After manual spec edits
 # 4. After webhook from ADO
 #

package/plugins/specweave-ado/lib/ado-project-detector.js

@@ -483,7 +483,7 @@ ${PROJECT_KEYWORDS[projectName]?.join(", ") || "TBD"}
 
 ## Getting Started
 
-1. Create a new spec: \`/specweave:increment "feature-name"\`
+1. Create a new spec: \`/sw:increment "feature-name"\`
 2. Specs will be organized here automatically
 3. Sync to Azure DevOps: \`/specweave-ado:sync-spec spec-001\`
 

package/plugins/specweave-ado/lib/ado-project-detector.ts

@@ -547,7 +547,7 @@ ${PROJECT_KEYWORDS[projectName]?.join(', ') || 'TBD'}
 
 ## Getting Started
 
-1. Create a new spec: \`/specweave:increment "feature-name"\`
+1. Create a new spec: \`/sw:increment "feature-name"\`
 2. Specs will be organized here automatically
 3. Sync to Azure DevOps: \`/specweave-ado:sync-spec spec-001\`
 

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

@@ -1,5 +1,5 @@
 ---
-name: specweave-ado-mapper
+name: ado-mapper
 description: Expert in bidirectional conversion between SpecWeave increments and Azure DevOps (ADO) Epics/Features/User Stories/Tasks. Handles export (increment → ADO), import (ADO → increment), and bidirectional sync with conflict resolution. Activates for ADO sync, Azure DevOps sync, work item creation, import from ADO.
 tools: Read, Write, Edit, Bash
 model: claude-opus-4-5-20251101
@@ -448,7 +448,7 @@ Validate all conversions using test cases in `test-cases/`:
 
 **Run tests**:
 ```bash
-npm run test:agents:specweave-ado-mapper
+npm run test:agents:ado-mapper
 ```
 
 ---

package/plugins/specweave-ado/skills/ado-multi-project/SKILL.md

@@ -284,7 +284,7 @@ This folder contains specifications for the {Project} project.
 ### Sync Increment to Projects
 
 ```bash
-/specweave-ado:sync-increment 0014
+/sw-ado:sync-increment 0014
 
 # Detects projects from spec
 # Creates work items in each project
@@ -294,7 +294,7 @@ This folder contains specifications for the {Project} project.
 ### Sync Spec to Project
 
 ```bash
-/specweave-ado:sync-spec AuthService/spec-001
+/sw-ado:sync-spec AuthService/spec-001
 
 # Syncs single spec to specific project
 # Updates existing work item or creates new
@@ -303,7 +303,7 @@ This folder contains specifications for the {Project} project.
 ### Sync All Specs
 
 ```bash
-/specweave-ado:sync-all
+/sw-ado:sync-all
 
 # Syncs all specs across all projects
 # Maintains relationships
@@ -430,9 +430,9 @@ Related Specs:
 
 Prefix increment names with primary project:
 ```bash
-/specweave:increment "payment-stripe-integration"
-/specweave:increment "auth-oauth-provider"
-/specweave:increment "user-profile-redesign"
+/sw:increment "payment-stripe-integration"
+/sw:increment "auth-oauth-provider"
+/sw:increment "user-profile-redesign"
 ```
 
 ## Error Handling

package/plugins/specweave-ado/skills/ado-resource-validator/SKILL.md

@@ -25,7 +25,7 @@ This skill ensures your Azure DevOps configuration in `.env` is valid and all re
 
 ✅ **Automatically activates when**:
 - You set up Azure DevOps integration for the first time
-- You run `/specweave-ado:sync` and resources are missing
+- You run `/sw-ado:sync` and resources are missing
 - Your `.env` has invalid Azure DevOps configuration
 - You mention "ado setup" or "azure devops validation"
 
@@ -227,7 +227,7 @@ Checking teams...
 
 **Scenario**: New setup with multiple projects for different teams
 
-**Action**: Run `/specweave-ado:sync`
+**Action**: Run `/sw-ado:sync`
 
 **What Happens**:
 ```bash
@@ -462,7 +462,7 @@ export async function validateAzureDevOpsResources(
 npx specweave init
 
 # Also runs automatically before sync
-/specweave-ado:sync 0014
+/sw-ado:sync 0014
 ```
 
 **Manual validation**:
@@ -751,10 +751,10 @@ Contact Azure DevOps support for limit increases.
 
 ### Automatic Validation
 
-When using `/specweave-ado:sync`, validation runs automatically:
+When using `/sw-ado:sync`, validation runs automatically:
 
 ```bash
-/specweave-ado:sync 0014
+/sw-ado:sync 0014
 
 # Internally calls:
 1. validateAzureDevOpsResources()

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

@@ -1,6 +1,6 @@
 ---
 name: ado-sync
-description: Bidirectional synchronization between SpecWeave increments and Azure DevOps work items (two-way sync by default). Activates ONLY when user asks questions about Azure DevOps integration or needs help configuring ADO sync. Does NOT activate for slash commands. For syncing, use /specweave-ado:sync command instead.
+description: Bidirectional synchronization between SpecWeave increments and Azure DevOps work items (two-way sync by default). Activates ONLY when user asks questions about Azure DevOps integration or needs help configuring ADO sync. Does NOT activate for slash commands. For syncing, use /sw-ado:sync command instead.
 ---
 
 # Azure DevOps Sync Skill
@@ -9,7 +9,7 @@ description: Bidirectional synchronization between SpecWeave increments and Azur
 
 **Default Behavior**: **Bidirectional (two-way) sync** - Changes in either system are automatically synchronized
 
-**⚠️ IMPORTANT**: This skill provides HELP and GUIDANCE about Azure DevOps sync. For actual syncing, users should use the `/specweave-ado:sync` command directly. This skill should NOT auto-activate when the command is being invoked.
+**⚠️ IMPORTANT**: This skill provides HELP and GUIDANCE about Azure DevOps sync. For actual syncing, users should use the `/sw-ado:sync` command directly. This skill should NOT auto-activate when the command is being invoked.
 
 **Capabilities**:
 - Bidirectional sync: SpecWeave ↔ ADO (default)
@@ -31,7 +31,7 @@ description: Bidirectional synchronization between SpecWeave increments and Azur
 - User needs help configuring Azure DevOps integration
 
 ❌ **Do NOT activate when**:
-- User invokes `/specweave-ado:sync` command (command handles it)
+- User invokes `/sw-ado:sync` command (command handles it)
 - Command is already running (avoid duplicate invocation)
 - Task completion hook is syncing (automatic process)
 - "Close ADO work item when done"
@@ -87,13 +87,13 @@ Add to `.specweave/config.json`:
 
 ## Commands Available
 
-### `/specweave-ado:create-workitem <increment-id>`
+### `/sw-ado:create-workitem <increment-id>`
 
 **Purpose**: Create ADO work item from increment
 
 **Example**:
 ```bash
-/specweave-ado:create-workitem 0005
+/sw-ado:create-workitem 0005
 ```
 
 **Result**:
@@ -104,13 +104,13 @@ Add to `.specweave/config.json`:
 
 ---
 
-### `/specweave-ado:sync <increment-id>`
+### `/sw-ado:sync <increment-id>`
 
 **Purpose**: Sync increment progress with ADO work item
 
 **Example**:
 ```bash
-/specweave-ado:sync 0005
+/sw-ado:sync 0005
 ```
 
 **Result**:
@@ -121,13 +121,13 @@ Add to `.specweave/config.json`:
 
 ---
 
-### `/specweave-ado:close-workitem <increment-id>`
+### `/sw-ado:close-workitem <increment-id>`
 
 **Purpose**: Close ADO work item when increment complete
 
 **Example**:
 ```bash
-/specweave-ado:close-workitem 0005
+/sw-ado:close-workitem 0005
 ```
 
 **Result**:
@@ -137,13 +137,13 @@ Add to `.specweave/config.json`:
 
 ---
 
-### `/specweave-ado:status <increment-id>`
+### `/sw-ado:status <increment-id>`
 
 **Purpose**: Check ADO sync status for increment
 
 **Example**:
 ```bash
-/specweave-ado:status 0005
+/sw-ado:status 0005
 ```
 
 **Result**:
@@ -193,10 +193,10 @@ Sync Enabled: ✅
 
 ### When Increment Completes
 
-**Trigger**: `/specweave:done` command
+**Trigger**: `/sw:done` command
 
 **Flow**:
-1. User runs `/specweave:done 0005`
+1. User runs `/sw:done 0005`
 2. Validate all tasks complete
 3. Close ADO work item automatically
 4. Add completion comment with summary
@@ -353,10 +353,10 @@ Sync Enabled: ✅
 
 ## Related Commands
 
-- `/specweave:inc` - Create increment (auto-creates ADO work item if enabled)
-- `/specweave:do` - Execute tasks (auto-syncs progress to ADO)
-- `/specweave:done` - Complete increment (auto-closes ADO work item)
-- `/specweave:status` - Show increment status (includes ADO sync status)
+- `/sw:inc` - Create increment (auto-creates ADO work item if enabled)
+- `/sw:do` - Execute tasks (auto-syncs progress to ADO)
+- `/sw:done` - Complete increment (auto-closes ADO work item)
+- `/sw:status` - Show increment status (includes ADO sync status)
 
 ---
 
@@ -381,7 +381,7 @@ Sync Enabled: ✅
 # User completed 3 tasks manually
 # Now sync to ADO
 
-/specweave-ado:sync 0005
+/sw-ado:sync 0005
 
 # Result: ADO Epic #12345 updated with 30% progress
 ```
@@ -389,7 +389,7 @@ Sync Enabled: ✅
 ### Example 3: Check Sync Status
 
 ```bash
-/specweave-ado:status 0005
+/sw-ado:status 0005
 
 # Output:
 # Work Item: #12345

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

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-alternatives",
+  "name": "sw-alternatives",
   "version": "0.24.0",
   "description": "Technology stack alternatives analysis using BMAD method - Best, Most Appropriate, Design decisions for architecture choices",
   "author": {

package/plugins/specweave-alternatives/commands/alternatives-analyze.md

@@ -5,7 +5,7 @@ Analyze technology stack alternatives using the **BMAD** (Best, Most Appropriate
 ## Usage
 
 ```
-/specweave-alternatives:alternatives-analyze <category> [context] [options]
+/sw-alternatives:alternatives-analyze <category> [context] [options]
 ```
 
 ## What I Do
@@ -20,7 +20,7 @@ Analyze technology stack alternatives using the **BMAD** (Best, Most Appropriate
 
 ### 1. Databases
 ```bash
-/specweave-alternatives:alternatives-analyze database \
+/sw-alternatives:alternatives-analyze database \
   --requirements "high-throughput,strong-consistency,cloud-native" \
   --scale "startup"
 ```
@@ -29,7 +29,7 @@ Analyze technology stack alternatives using the **BMAD** (Best, Most Appropriate
 
 ### 2. Backend Frameworks
 ```bash
-/specweave-alternatives:alternatives-analyze backend-framework \
+/sw-alternatives:alternatives-analyze backend-framework \
   --language typescript \
   --requirements "fast-development,type-safe,good-orms"
 ```
@@ -38,7 +38,7 @@ Analyze technology stack alternatives using the **BMAD** (Best, Most Appropriate
 
 ### 3. Frontend Frameworks
 ```bash
-/specweave-alternatives:alternatives-analyze frontend-framework \
+/sw-alternatives:alternatives-analyze frontend-framework \
   --requirements "SEO,performance,large-team" \
   --existing-stack "React"
 ```
@@ -47,7 +47,7 @@ Analyze technology stack alternatives using the **BMAD** (Best, Most Appropriate
 
 ### 4. Cloud Providers
 ```bash
-/specweave-alternatives:alternatives-analyze cloud-provider \
+/sw-alternatives:alternatives-analyze cloud-provider \
   --workload "containerized-microservices" \
   --scale "enterprise" \
   --constraints "EU-data-residency"
@@ -57,7 +57,7 @@ Analyze technology stack alternatives using the **BMAD** (Best, Most Appropriate
 
 ### 5. Message Queues
 ```bash
-/specweave-alternatives:alternatives-analyze message-queue \
+/sw-alternatives:alternatives-analyze message-queue \
   --requirements "exactly-once,high-throughput,stream-processing" \
   --scale "100k-msgs-sec"
 ```
@@ -66,7 +66,7 @@ Analyze technology stack alternatives using the **BMAD** (Best, Most Appropriate
 
 ### 6. Authentication
 ```bash
-/specweave-alternatives:alternatives-analyze auth \
+/sw-alternatives:alternatives-analyze auth \
   --requirements "social-login,SSO,MFA,compliance" \
   --constraints "GDPR,SOC2"
 ```
@@ -272,7 +272,7 @@ Choose technologies that match team expertise or learning goals.
 
 ### Analyze Database Options
 ```bash
-/specweave-alternatives:alternatives-analyze database \
+/sw-alternatives:alternatives-analyze database \
   --scale startup \
   --budget 200 \
   --requirements "ACID,JSON-support,full-text-search" \
@@ -281,7 +281,7 @@ Choose technologies that match team expertise or learning goals.
 
 ### Compare Cloud Providers
 ```bash
-/specweave-alternatives:alternatives-analyze cloud-provider \
+/sw-alternatives:alternatives-analyze cloud-provider \
   --workload "containerized-apps" \
   --scale "scale-up" \
   --budget 5000 \
@@ -290,7 +290,7 @@ Choose technologies that match team expertise or learning goals.
 
 ### Frontend Framework Decision
 ```bash
-/specweave-alternatives:alternatives-analyze frontend-framework \
+/sw-alternatives:alternatives-analyze frontend-framework \
   --existing-stack React \
   --requirements "SEO,SSR,static-generation" \
   --team-size 8
@@ -298,7 +298,7 @@ Choose technologies that match team expertise or learning goals.
 
 ### Message Queue Selection
 ```bash
-/specweave-alternatives:alternatives-analyze message-queue \
+/sw-alternatives:alternatives-analyze message-queue \
   --scale enterprise \
   --requirements "exactly-once,replay,stream-processing" \
   --throughput "500k-msgs-sec"
@@ -306,9 +306,9 @@ Choose technologies that match team expertise or learning goals.
 
 ## Related Commands
 
-- `/specweave-alternatives:cost-compare` - Detailed cost comparison only
-- `/specweave-alternatives:migration-plan` - Generate migration plan from A to B
-- `/specweave-cost-optimizer:analyze` - Optimize costs for chosen stack
+- `/sw-alternatives:cost-compare` - Detailed cost comparison only
+- `/sw-alternatives:migration-plan` - Generate migration plan from A to B
+- `/sw-cost:analyze` - Optimize costs for chosen stack
 
 ## Best Practices
 

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

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-backend",
+  "name": "sw-backend",
   "description": "Backend API development for Node.js, Python, and .NET stacks. Includes Express, NestJS, FastAPI, Django, Flask, ASP.NET Core, and Entity Framework Core. Focus on REST APIs, authentication, database operations, and background services.",
   "version": "0.22.14",
   "author": {

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

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-confluent",
+  "name": "sw-confluent",
   "description": "Confluent Cloud integration for SpecWeave - Schema Registry, ksqlDB, Kafka Connect, Flink, stream processing, and enterprise Kafka features",
   "version": "0.22.14",
   "author": {

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

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-cost-optimizer",
+  "name": "sw-cost",
   "description": "Cloud cost optimization and analysis for AWS, Azure, GCP, and serverless platforms. Provides cost analysis, optimization recommendations, pricing comparisons, budget alerts, and serverless cost modeling with 2024/2025 pricing.",
   "version": "0.24.0",
   "author": {

package/plugins/specweave-cost-optimizer/commands/cost-analyze.md

@@ -1,4 +1,4 @@
-# /specweave-cost-optimizer:cost-analyze
+# /sw-cost:cost-analyze
 
 Analyze cloud infrastructure costs and identify optimization opportunities across AWS, Azure, and GCP.
 

package/plugins/specweave-cost-optimizer/commands/cost-optimize.md

@@ -1,4 +1,4 @@
-# /specweave-cost-optimizer:cost-optimize
+# /sw-cost:cost-optimize
 
 Implement cost optimization recommendations with automated resource modifications and savings plan purchases.
 

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

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-diagrams",
+  "name": "sw-diagrams",
   "description": "Architecture diagram generation with Mermaid following C4 Model conventions. Creates C4 Context/Container/Component diagrams, sequence diagrams, ER diagrams, and deployment diagrams. SpecWeave-aware for HLD/LLD documentation.",
   "version": "0.24.0",
   "author": {

package/plugins/specweave-diagrams/commands/diagrams-generate.md

@@ -1,4 +1,4 @@
-# /specweave-diagrams:diagrams-generate
+# /sw-diagrams:diagrams-generate
 
 Generate Mermaid architecture diagrams following C4 Model conventions.
 

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

@@ -1,5 +1,5 @@
 {
-  "name": "specweave-docs",
+  "name": "sw-docs",
   "version": "0.24.0",
   "description": "Documentation generation and management - Docusaurus, spec-driven docs, API documentation, living documentation",
   "author": {

package/plugins/specweave-docs/commands/build.md

@@ -1,5 +1,5 @@
 ---
-name: specweave-docs:build
+name: sw-docs:build
 description: Build static documentation site for deployment. Validates docs first, auto-fixes issues, auto-setup on first run. Outputs production-ready HTML/CSS/JS.
 ---
 
@@ -52,7 +52,7 @@ if [ ! -d ".specweave/cache/docs-site/node_modules" ]; then
 fi
 ```
 
-If not set up, follow the same setup steps as `/specweave-docs:preview` (Step 3 in preview.md).
+If not set up, follow the same setup steps as `/sw-docs:view` (Step 3 in view.md).
 
 ### Step 3: Run Build
 
@@ -131,10 +131,10 @@ git commit -m "docs: update documentation site"
 
 ### Build fails with broken links
 ```bash
-# Preview first to find errors
-/specweave-docs:preview
+# View docs first to find errors
+/sw-docs:view
 # Fix broken links, then build
-/specweave-docs:build
+/sw-docs:build
 ```
 
 ### Out of memory
@@ -150,11 +150,11 @@ cd .specweave/cache/docs-site && npm run clear && npm run build
 ### Reinstall from scratch
 ```bash
 rm -rf .specweave/cache/docs-site
-/specweave-docs:build
+/sw-docs:build
 ```
 
 ## See Also
 
-- `/specweave-docs:preview` - Preview docs locally with hot reload
-- `/specweave-docs:organize` - Organize large folders with themed indexes
-- `/specweave-docs:health` - Documentation health report
+- `/sw-docs:view` - View docs locally with hot reload
+- `/sw-docs:organize` - Organize large folders with themed indexes
+- `/sw-docs:health` - Documentation health report