@sniper.ai/cli 1.0.1 → 2.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +76 -2
- package/dist/index.js +957 -26
- package/dist/index.js.map +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,6 +1,32 @@
|
|
|
1
1
|
# @sniper.ai/cli
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
[](https://www.npmjs.com/package/@sniper.ai/cli)
|
|
4
|
+
[](https://opensource.org/licenses/MIT)
|
|
5
|
+
|
|
6
|
+
CLI tool for scaffolding and managing [SNIPER](https://virkt25.github.io/sniper/)-enabled projects.
|
|
7
|
+
|
|
8
|
+
## What is SNIPER?
|
|
9
|
+
|
|
10
|
+
SNIPER (**S**pawn, **N**avigate, **I**mplement, **P**arallelize, **E**valuate, **R**elease) is an AI-powered project lifecycle framework that orchestrates Claude Code agent teams through structured phases -- from discovery and planning through implementation and release. Each phase spawns coordinated teams of specialized agents composed from layered personas.
|
|
11
|
+
|
|
12
|
+
## Quick Start
|
|
13
|
+
|
|
14
|
+
```bash
|
|
15
|
+
# 1. Install the CLI globally
|
|
16
|
+
npm install -g @sniper.ai/cli
|
|
17
|
+
|
|
18
|
+
# 2. Initialize SNIPER in your project
|
|
19
|
+
sniper init
|
|
20
|
+
|
|
21
|
+
# 3. (Optional) Add a domain pack for project-specific context
|
|
22
|
+
sniper add-pack @sniper.ai/pack-sales-dialer
|
|
23
|
+
|
|
24
|
+
# 4. Run the lifecycle phases in Claude Code
|
|
25
|
+
/sniper-discover # Phase 1: Discovery & Analysis
|
|
26
|
+
/sniper-plan # Phase 2: Planning & Architecture
|
|
27
|
+
/sniper-solve # Phase 3: Epic Sharding & Stories
|
|
28
|
+
/sniper-sprint # Phase 4: Implementation Sprint
|
|
29
|
+
```
|
|
4
30
|
|
|
5
31
|
## Installation
|
|
6
32
|
|
|
@@ -8,7 +34,9 @@ CLI tool for scaffolding and managing SNIPER-enabled projects.
|
|
|
8
34
|
npm install -g @sniper.ai/cli
|
|
9
35
|
```
|
|
10
36
|
|
|
11
|
-
## Commands
|
|
37
|
+
## CLI Commands (Terminal)
|
|
38
|
+
|
|
39
|
+
These commands are run in your terminal to manage the SNIPER installation.
|
|
12
40
|
|
|
13
41
|
### `sniper init`
|
|
14
42
|
|
|
@@ -58,6 +86,48 @@ List all installed domain packs.
|
|
|
58
86
|
sniper list-packs
|
|
59
87
|
```
|
|
60
88
|
|
|
89
|
+
## Slash Commands (Claude Code)
|
|
90
|
+
|
|
91
|
+
Once SNIPER is initialized, these slash commands are available inside Claude Code. They drive the agent team lifecycle.
|
|
92
|
+
|
|
93
|
+
### Lifecycle
|
|
94
|
+
|
|
95
|
+
| Command | Description |
|
|
96
|
+
|---------|-------------|
|
|
97
|
+
| `/sniper-init` | Initialize SNIPER in a new or existing project |
|
|
98
|
+
| `/sniper-discover` | Phase 1: Discovery and analysis (parallel team) |
|
|
99
|
+
| `/sniper-plan` | Phase 2: Planning and architecture (parallel team with coordination) |
|
|
100
|
+
| `/sniper-solve` | Phase 3: Epic sharding and story creation (single agent) |
|
|
101
|
+
| `/sniper-sprint` | Phase 4: Implementation sprint (parallel team) |
|
|
102
|
+
| `/sniper-review` | Run review gate for the current phase |
|
|
103
|
+
| `/sniper-status` | Show lifecycle status and artifact state |
|
|
104
|
+
|
|
105
|
+
### Extended
|
|
106
|
+
|
|
107
|
+
| Command | Description |
|
|
108
|
+
|---------|-------------|
|
|
109
|
+
| `/sniper-feature` | Incremental feature lifecycle |
|
|
110
|
+
| `/sniper-ingest` | Codebase ingestion (parallel team) |
|
|
111
|
+
| `/sniper-doc` | Generate or update project documentation (parallel team) |
|
|
112
|
+
| `/sniper-debug` | Production debugging (phased investigation) |
|
|
113
|
+
| `/sniper-audit` | Audit: refactoring, review, and QA |
|
|
114
|
+
|
|
115
|
+
### Workspace
|
|
116
|
+
|
|
117
|
+
| Command | Description |
|
|
118
|
+
|---------|-------------|
|
|
119
|
+
| `/sniper-workspace init` | Initialize a SNIPER workspace |
|
|
120
|
+
| `/sniper-workspace feature` | Plan and execute a cross-repo feature |
|
|
121
|
+
| `/sniper-workspace status` | Show workspace status |
|
|
122
|
+
| `/sniper-workspace validate` | Validate interface contracts |
|
|
123
|
+
|
|
124
|
+
### Utility
|
|
125
|
+
|
|
126
|
+
| Command | Description |
|
|
127
|
+
|---------|-------------|
|
|
128
|
+
| `/sniper-compose` | Compose a spawn prompt from persona layers |
|
|
129
|
+
| `/sniper-memory` | Manage agent memory (conventions, anti-patterns, decisions) |
|
|
130
|
+
|
|
61
131
|
## How It Works
|
|
62
132
|
|
|
63
133
|
The CLI reads framework content from `@sniper.ai/core` and scaffolds it into your project's `.sniper/` directory. This gives Claude Code access to personas, team definitions, templates, and slash commands that drive the SNIPER lifecycle.
|
|
@@ -78,6 +148,10 @@ pnpm dev # Watch mode
|
|
|
78
148
|
pnpm build # Production build
|
|
79
149
|
```
|
|
80
150
|
|
|
151
|
+
## Documentation
|
|
152
|
+
|
|
153
|
+
Full documentation is available at [virkt25.github.io/sniper](https://virkt25.github.io/sniper/).
|
|
154
|
+
|
|
81
155
|
## License
|
|
82
156
|
|
|
83
157
|
MIT
|