specweave 1.0.214 → 1.0.215

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specweave",
-  "version": "1.0.214",
+  "version": "1.0.215",
   "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",

package/plugins/specweave/commands/abandon.md

@@ -1,7 +1,7 @@
 ---
 name: abandon
 description: Abandon an incomplete increment (requirements changed, obsolete)
-usage: /sw:abandon <increment-id> --reason="<reason>"
+argument-hint: [increment-id] --reason="reason"
 ---
 
 # Abandon Increment Command

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

@@ -1,7 +1,7 @@
 ---
 name: api-docs
 description: Generate and synchronize API documentation - OpenAPI spec, Postman collection with environments, and API client SDKs. Framework-aware with auto-detection. For API projects only.
-usage: /sw:api-docs [--openapi] [--postman] [--env] [--all] [--watch] [--validate] [--framework <name>]
+argument-hint: [--openapi] [--postman] [--all] [--validate]
 ---
 
 # API Documentation Generator

package/plugins/specweave/commands/backlog.md

@@ -1,7 +1,7 @@
 ---
 name: backlog
 description: Move an increment to backlog (planned but not ready to start)
-usage: /sw:backlog <increment-id> --reason="<reason>"
+argument-hint: [increment-id] --reason="reason"
 ---
 
 # Backlog Increment Command

package/plugins/specweave/commands/external.md

@@ -1,7 +1,7 @@
 ---
 name: external
 description: View external items dashboard - open issues from GitHub, JIRA, and Azure DevOps
-usage: /sw:external [--refresh]
+argument-hint: [--refresh]
 ---
 
 # External Items Dashboard

package/plugins/specweave/commands/jobs.md

@@ -1,7 +1,7 @@
 ---
 name: jobs
 description: Show current work status (active increments, progress) and background jobs (imports, cloning). Even with no jobs, shows increment summary and helpful context.
-usage: /sw:jobs [--all] [--id <job-id>]
+argument-hint: [--all] [--id job-id]
 ---
 
 # Background Jobs Monitor

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

@@ -1,7 +1,7 @@
 ---
 name: living-docs
 description: Launch or resume Living Docs Builder independently. Generates comprehensive enterprise documentation from codebase analysis with AI-powered insights. LSP-enhanced by default for accurate API extraction.
-usage: /sw:living-docs [--resume <jobId>] [--depth <level>] [--priority <modules>] [--sources <folders>] [--depends-on <jobIds>] [--foreground] [--full-scan] [--no-lsp]
+argument-hint: [--resume jobId] [--depth level] [--full-scan]
 ---
 
 # Living Docs Builder (Standalone)

package/plugins/specweave/commands/pause.md

@@ -1,7 +1,7 @@
 ---
 name: pause
 description: Pause an active increment (blocked by external dependency, deprioritized)
-usage: /sw:pause <increment-id> --reason="<reason>"
+argument-hint: [increment-id] --reason="reason"
 ---
 
 # Pause Increment Command

package/plugins/specweave/commands/resume.md

@@ -1,7 +1,7 @@
 ---
 name: resume
 description: Resume a paused or backlog increment
-usage: /sw:resume <increment-id>
+argument-hint: [increment-id]
 ---
 
 # Resume Increment Command

package/plugins/specweave/commands/skill-match.md

@@ -1,13 +1,7 @@
 ---
 name: skill-match
 description: Test a prompt against skill triggers to see what would match
-trigger: /sw:skill-match
-category: debugging
-arguments:
-  - name: prompt
-    description: The prompt to test
-    required: true
-    type: string
+argument-hint: [prompt]
 ---
 
 # Skill Match Command

package/plugins/specweave/commands/skill.md

@@ -1,4 +1,10 @@
-# /sw:skill
+---
+name: skill
+description: Create Claude Code skills with proper YAML frontmatter, validation, and best practices
+argument-hint: [--name skill-name] [--type auto|command|knowledge]
+---
+
+# Skill Creator
 
 Create Claude Code skills with proper YAML frontmatter, validation, and best practices.
 

package/plugins/specweave/commands/status.md

@@ -1,7 +1,7 @@
 ---
 name: status
 description: Show increment status overview with rich details (active, backlog, paused, completed, abandoned)
-usage: /sw:status [--active|--backlog|--paused|--completed|--abandoned|--stale]
+argument-hint: [--active|--backlog|--paused|--completed|--abandoned]
 ---
 
 # Increment Status

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

@@ -1,16 +0,0 @@
----
-name: ado-manager
-description: Azure DevOps integration specialist for SpecWeave increments with epic/feature/story management and bidirectional sync. Use when creating ADO work items, syncing task completion, or troubleshooting ADO API issues. Covers rate limiting, WIQL queries, and area path configuration.
-role: Azure DevOps Integration Specialist
-context: |
-  You are an expert in Azure DevOps (ADO) REST API integration, work item management, and SpecWeave increment synchronization.
-
-  Your responsibilities:
-  - Create and manage ADO work items (Epics, Features, User Stories)
-  - Sync SpecWeave increment progress to ADO
-  - Handle bidirectional sync (ADO ↔ SpecWeave)
-  - Troubleshoot ADO API issues
-  - Optimize sync performance and rate limiting
-model: opus
-context: fork
----

package/plugins/specweave-infrastructure/skills/network-engineer/SKILL.md

@@ -1,12 +0,0 @@
----
-name: network-engineer
-description: Cloud network architect for VPC design, service mesh, zero-trust networking, load balancers, and CDN optimization. Use for network troubleshooting or connectivity issues.
-model: opus
-context: fork
----
-
-## ⚠️ Chunking for Large Network Architectures
-
-When generating comprehensive network architectures that exceed 1000 lines (e.g., complete multi-cloud network design with VPCs, subnets, routing, load balancing, service mesh, and security policies), generate output **incrementally** to prevent crashes. Break large network implementations into logical layers (e.g., VPC & Subnets → Routing → Load Balancing → Service Mesh → Security Policies) and ask the user which layer to design next. This ensures reliable delivery of network architecture without overwhelming the system.
-
-You are a network engineer specializing in modern cloud networking, security, and performance optimization.

package/plugins/specweave-infrastructure/skills/performance-engineer/SKILL.md

@@ -1,12 +0,0 @@
----
-name: performance-engineer
-description: Performance engineering - OpenTelemetry, distributed tracing, load testing (k6, JMeter), multi-tier caching, Core Web Vitals. Use for slow apps or latency issues.
-model: opus
-context: fork
----
-
-## ⚠️ Chunking for Large Performance Optimization Plans
-
-When generating comprehensive performance optimization implementations that exceed 1000 lines (e.g., complete performance stack with distributed tracing, multi-tier caching, load testing setup, and Core Web Vitals optimization), generate output **incrementally** to prevent crashes. Break large performance projects into logical components (e.g., Profiling & Baselining → Caching Strategy → Database Optimization → Load Testing → Monitoring Setup) and ask the user which component to implement next. This ensures reliable delivery of performance infrastructure without overwhelming the system.
-
-You are a performance engineer specializing in modern application optimization, observability, and scalable system performance.

package/plugins/specweave-infrastructure/skills/sre/SKILL.md

@@ -1,13 +0,0 @@
----
-name: sre
-description: SRE expert for incident response, production troubleshooting, root cause analysis, post-mortems, and runbooks. Use for outages, performance issues, or SEV incidents.
-allowed-tools: Read, Bash, Grep
-model: opus
-context: fork
----
-
-# SRE Agent - Site Reliability Engineering Expert
-
-## ⚠️ Chunking for Large Incident Reports
-
-When generating comprehensive incident reports that exceed 1000 lines (e.g., complete post-mortems covering root cause analysis, mitigation plans, runbooks, and preventive measures across multiple system layers), generate output **incrementally** to prevent crashes. Break large incident reports into logical phases (e.g., Triage → Root Cause Analysis → Immediate Mitigation → Long-term Prevention → Post-Mortem) and ask the user which phase to work on next. This ensures reliable delivery of SRE documentation without overwhelming the system.