Reference Documentation
Complete reference for all SpecWeave skills, commands, and capabilities.
What's the Difference?
| Type | Purpose | Example |
|---|---|---|
| Skills | Domain expertise and best practices | sw:architect, /mobile:appstore |
| Commands | Execute specific actions | sw:auto, sw:done, sw:validate |
Both Are Slash Commands Now
In Claude Code, skills and commands are invoked the same way - with sw:name. Skills provide domain knowledge; commands perform actions.
Quick Navigation
Skills Reference
80+ specialized skills organized by domain:
- Core: Planning, architecture, orchestration
- Frontend: React, Vue, Next.js, design systems
- Backend: Node.js, Python, .NET, databases
- Infrastructure: DevOps, Kubernetes, observability
- Testing: TDD, E2E, quality gates
- Security: OWASP, compliance, threat modeling
- Data: Kafka, streaming, ML/AI
- And more: Mobile, payments, documentation, cost optimization
Commands Reference
All slash commands organized by purpose:
- Planning:
sw:increment - Execution:
sw:auto,sw:do,sw:auto-parallel - Quality:
sw:validate,sw:qa,sw:grill - Completion:
sw:next,sw:done - Sync:
sw-github:sync,sw-jira:sync,sw-ado:sync
Configuration Reference
Every config.json property documented with types, defaults, and examples:
- Quick reference table of all disableable features
- config.json sections: testing, living docs, sync, CI/CD, and more
- metadata.json fields for per-increment overrides
- Environment variables for runtime control
Use Case Guide
Find the right tool for your task:
- "I want to..." quick lookup tables
- Role-based recommendations (PM, Architect, Frontend, Backend, DevOps, QA)
- Phase-based workflows (Plan → Implement → Quality → Complete)
- Decision trees for choosing execution mode, quality checks, sync tools
Most Used
Planning
"Let's build a new feature"
sw:pm # Product management
sw:architect # System design
Execution
"Ship while I sleep"
sw:do # Manual task-by-task
sw:progress # Check status
Quality
"Check the quality of my work"
Additional: sw:qa --gate (AI quality gate), sw:grill (deep audit).
Completion
"What's next?"
Additional: sw-github:sync 0007 (sync to GitHub).
Plugin Ecosystem
Skills come from plugins. Core plugin sw is always installed. Domain plugins auto-load based on your tech stack:
| Plugin | Skills Count | Domain |
|---|---|---|
sw (core) | 44 | Planning, execution, quality, sync, utilities |
mobile | 1 | App Store Connect automation |
marketing | 3 | Marketing and social media |
google-workspace | 3 | Google Workspace CLI |
productivity | 1 | Personal productivity |
skills | 1 | Skill discovery |
Installing Plugins
# The sw plugin installs automatically via specweave init
# Domain plugins install manually:
npx vskill install --repo anton-abyzov/vskill --plugin mobile
npx vskill install --repo anton-abyzov/vskill --plugin marketing
npx vskill install --repo anton-abyzov/specweave --plugin sw
Next Steps
- Skills Reference - All skills by domain
- Commands Reference - All commands by purpose
- Configuration Reference - All config properties
- Use Case Guide - Find the right tool