SpecWeave command reference and help. Shows available commands. DO NOT use routing syntax like '/specweave do' - always use full namespaced commands like '/sw:do' instead.
Shows all available SpecWeave commands and their usage patterns. Use this when you need to reference the correct command syntax, especially the critical difference between `/sw:do` (correct) and `/specweave do` (incorrect).
/plugin marketplace add anton-abyzov/specweave/plugin install sw@specweave⚠️ IMPORTANT: This is a REFERENCE ONLY, not a router!
DO NOT use: /specweave do, /specweave inc, etc.
ALWAYS use: /sw:do, /sw:increment, etc.
Claude Code does not support command routing. Each command must be invoked directly by its full namespaced name.
Namespace Protection: All SpecWeave commands are prefixed with specweave: to avoid collisions with existing project commands.
All commands use the specweave: prefix (note the colon!)
| Command | Description | Example |
|---|---|---|
/sw:increment | Create new increment (PM-led) | /sw:increment "User auth" |
/sw:do | Execute tasks (auto-resumes) | /sw:do or /sw:do 0031 |
/sw:next | Smart transition (close + suggest) | /sw:next |
/sw:done | Manual closure with PM validation | /sw:done 0031 |
/sw:progress | Check status and next action | /sw:progress |
/sw:validate | Validate increment quality | /sw:validate 0031 |
| Command | Description | Example |
|---|---|---|
/sw:sync-docs | Sync living docs | /sw:sync-docs update |
/sw:sync-tasks | Sync tasks with status | /sw:sync-tasks |
| Command | Description | Example |
|---|---|---|
/sw-github:create-issue | Create GitHub issue | /sw-github:create-issue 0031 |
/sw-github:sync | Two-way sync | /sw-github:sync 0031 |
/sw-github:sync-tasks | Sync tasks as sub-issues | /sw-github:sync-tasks 0031 |
/sw-github:close-issue | Close GitHub issue | /sw-github:close-issue 0031 |
/sw-github:status | Show sync status | /sw-github:status |
Claude Code does not implement command routing!
This file is a reference guide only. You cannot do:
/specweave do (doesn't work, no routing!)/specweave inc "feature" (doesn't work!)/specweave next (doesn't work!)Instead, always use full namespaced commands:
/sw:do/sw:increment "feature"/sw:nextWhy This Matters:
Calling both /specweave and /sw:do causes duplicate invocations! Always use the namespaced version with the colon.
# Create increment
/sw:increment "User authentication"
# Execute tasks
/sw:do
# Check progress
/sw:progress
# Complete increment
/sw:done 0031
# DO NOT use routing syntax:
/specweave do # ❌ Won't work, no routing!
/specweave inc "feat" # ❌ Won't work!
/specweave next # ❌ Won't work!
# ALWAYS use namespaced commands:
/sw:do # ✅ Correct!
/sw:increment "feat" # ✅ Correct!
/sw:next # ✅ Correct!
Namespace Protection: All SpecWeave commands use specweave: prefix to avoid collisions with existing project commands in brownfield setups.
Benefits:
specweave: prefix shows it's a framework commandspecweave:* commands, user's commands intact⚠️ Remember: Always use /sw: with a colon, never /specweave with a space!