Commands Reference
SNIPER v3 provides five slash commands invoked in Claude Code. The core command is /sniper-flow, which replaces v2's per-phase commands with a single protocol execution engine.
Commands
| Command | Description |
|---|---|
/sniper-flow | Execute a protocol — auto-detects scope or use --protocol <name> |
/sniper-init | Initialize SNIPER v3 in a new or existing project |
/sniper-learn | Submit, review, or deprecate project learnings |
/sniper-review | Manually trigger a review gate for the current phase |
/sniper-status | Show current protocol progress |
Quick Start
16 lines
bash
# Initialize SNIPER in your project
/sniper-init
# Run the full lifecycle (auto-detects scope)
/sniper-flow
# Run a specific protocol
/sniper-flow --protocol feature
/sniper-flow --protocol patch
/sniper-flow --protocol ingest
# Resume an interrupted protocol
/sniper-flow --resume
# Check progress
/sniper-statusProtocols
/sniper-flow executes one of seven protocols. Use --protocol <name> to pick one explicitly, or let SNIPER auto-detect from your project state.
| Protocol | Phases | Use Case |
|---|---|---|
full | discover → define → design → solve → implement → review → retro | Greenfield projects, major features |
feature | define → design → solve → implement → review → retro | Adding features to existing projects |
patch | implement → review | Small changes, bug fixes |
ingest | scan → document → extract | Reverse-engineering existing codebases |
explore | discover | Research and analysis only |
refactor | analyze → implement → review → retro | Code refactoring with safety analysis |
hotfix | implement | Emergency fixes, no gates |
Command Flow
All commands follow this pattern:
- State check — verify SNIPER is initialized and determine the current phase
- Protocol selection — auto-detect or use the specified protocol
- Agent spawning — spawn specialized agents defined by the protocol
- Phase execution — agents produce artifacts
- Quality gate — review checklist evaluation before advancing
TIP
Run /sniper-status at any time to see where you are in the lifecycle and what to do next.
Related
- Full Lifecycle — how phases connect end-to-end
- Review Gates — quality gates between phases
- Headless & CI/CD — running protocols in CI pipelines
- CLI Commands —
sniperbinary subcommands
