tracerkit 1.3.10 → 1.3.11
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 +106 -100
- package/dist/bin.js +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,12 +8,20 @@
|
|
|
8
8
|
[](https://www.npmjs.com/package/tracerkit)
|
|
9
9
|
[](https://opensource.org/licenses/MIT)
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Replace ad-hoc AI prompts with a repeatable three-step spec process — from idea to verified, archived code.
|
|
12
12
|
|
|
13
13
|
**Zero runtime dependencies** — pure Markdown skills, no build step.
|
|
14
14
|
|
|
15
15
|
</div>
|
|
16
16
|
|
|
17
|
+
## Why TracerKit?
|
|
18
|
+
|
|
19
|
+
AI coding without specs means vague prompts and lost context between sessions. Most planning tools produce horizontal task lists — nothing works until everything is done.
|
|
20
|
+
|
|
21
|
+
TracerKit uses **tracer-bullet vertical slices** instead: each phase cuts through every layer (schema → service → API → UI → tests), so every phase is demoable on its own. Integration problems surface early, context stays focused, and AI assistants get small, well-scoped phases instead of sprawling layers.
|
|
22
|
+
|
|
23
|
+
The term comes from [The Pragmatic Programmer](https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/).
|
|
24
|
+
|
|
17
25
|
## Get Started
|
|
18
26
|
|
|
19
27
|
### 1. Install TracerKit
|
|
@@ -24,9 +32,7 @@ npx tracerkit init
|
|
|
24
32
|
|
|
25
33
|
Skills are installed globally to `~/.claude/skills/` — available in every project, no per-project setup needed.
|
|
26
34
|
|
|
27
|
-
### 2. Use the
|
|
28
|
-
|
|
29
|
-
Open Claude Code in any project and start using:
|
|
35
|
+
### 2. Use the workflow
|
|
30
36
|
|
|
31
37
|
```bash
|
|
32
38
|
/tk:prd add dark mode support # define the feature
|
|
@@ -34,20 +40,6 @@ Open Claude Code in any project and start using:
|
|
|
34
40
|
/tk:verify dark-mode-support # verify and archive
|
|
35
41
|
```
|
|
36
42
|
|
|
37
|
-
### 3. CLI Reference
|
|
38
|
-
|
|
39
|
-
| Command | Description |
|
|
40
|
-
| -------------------------- | ---------------------------------------------- |
|
|
41
|
-
| `tracerkit init` | Install skills to `~/.claude/skills/` |
|
|
42
|
-
| `tracerkit init <path>` | Install skills to a specific project directory |
|
|
43
|
-
| `tracerkit update` | Refresh to latest version, skip modified files |
|
|
44
|
-
| `tracerkit update --force` | Replace modified files with latest versions |
|
|
45
|
-
| `tracerkit uninstall` | Remove TracerKit skills, keep user artifacts |
|
|
46
|
-
| `tracerkit --version` | Print version |
|
|
47
|
-
| `tracerkit --help` | Show help message |
|
|
48
|
-
|
|
49
|
-
All commands default to the home directory. Pass a path to target a specific project.
|
|
50
|
-
|
|
51
43
|
<details>
|
|
52
44
|
<summary>Per-project usage</summary>
|
|
53
45
|
|
|
@@ -93,88 +85,6 @@ Useful but optional — this category will grow over time.
|
|
|
93
85
|
|
|
94
86
|
Scans `prds/` and prints a table of all features grouped by status (`in_progress`, `created`, `done`), with age, latest verdict, and blocker/suggestion counts. Read-only — no files are modified.
|
|
95
87
|
|
|
96
|
-
## Metadata Lifecycle
|
|
97
|
-
|
|
98
|
-
Each PRD carries YAML frontmatter that tracks its position in the workflow. The skills update it automatically — you never need to edit it by hand.
|
|
99
|
-
|
|
100
|
-
**Fields:**
|
|
101
|
-
|
|
102
|
-
- `created` — ISO 8601 UTC timestamp, set when the PRD is written
|
|
103
|
-
- `status` — `created` | `in_progress` | `done`
|
|
104
|
-
- `completed` — ISO 8601 UTC timestamp, set when verification passes
|
|
105
|
-
|
|
106
|
-
**How it changes:**
|
|
107
|
-
|
|
108
|
-
| Stage | Skill | Frontmatter |
|
|
109
|
-
| -------- | ------------------- | ---------------------------------------------------- |
|
|
110
|
-
| Defined | `/tk:prd` | `created: 2025-06-15T14:30:00Z`<br>`status: created` |
|
|
111
|
-
| Planning | `/tk:plan` | `status: in_progress` |
|
|
112
|
-
| Verified | `/tk:verify` (PASS) | `status: done`<br>`completed: 2025-06-20T09:00:00Z` |
|
|
113
|
-
|
|
114
|
-
<details>
|
|
115
|
-
<summary>Example frontmatter at each stage</summary>
|
|
116
|
-
|
|
117
|
-
After `/tk:prd`:
|
|
118
|
-
|
|
119
|
-
```yaml
|
|
120
|
-
---
|
|
121
|
-
created: 2025-06-15T14:30:00Z
|
|
122
|
-
status: created
|
|
123
|
-
---
|
|
124
|
-
```
|
|
125
|
-
|
|
126
|
-
After `/tk:plan`:
|
|
127
|
-
|
|
128
|
-
```yaml
|
|
129
|
-
---
|
|
130
|
-
created: 2025-06-15T14:30:00Z
|
|
131
|
-
status: in_progress
|
|
132
|
-
---
|
|
133
|
-
```
|
|
134
|
-
|
|
135
|
-
After `/tk:verify` (PASS):
|
|
136
|
-
|
|
137
|
-
```yaml
|
|
138
|
-
---
|
|
139
|
-
created: 2025-06-15T14:30:00Z
|
|
140
|
-
status: done
|
|
141
|
-
completed: 2025-06-20T09:00:00Z
|
|
142
|
-
---
|
|
143
|
-
```
|
|
144
|
-
|
|
145
|
-
</details>
|
|
146
|
-
|
|
147
|
-
## Why TracerKit?
|
|
148
|
-
|
|
149
|
-
Most planning tools produce horizontal task lists — nothing works until everything is done. TracerKit uses **tracer-bullet vertical slices** instead: each phase cuts through every layer (schema → service → API → UI → tests), so every phase is demoable on its own. Integration problems surface early, context stays focused, and AI assistants get small well-scoped phases instead of sprawling layers.
|
|
150
|
-
|
|
151
|
-
The term comes from [The Pragmatic Programmer](https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/).
|
|
152
|
-
|
|
153
|
-
### Compared to
|
|
154
|
-
|
|
155
|
-
**vs. [Spec Kit](https://github.com/github/spec-kit)** (GitHub) — Thorough but heavyweight. 5 phases, Python setup, rigid phase gates. TracerKit is 3 phases, zero deps, automated verification.
|
|
156
|
-
|
|
157
|
-
**vs. [Kiro](https://kiro.dev/)** (AWS) — Powerful but locked to a dedicated IDE. TracerKit works inside Claude Code with pure Markdown skills.
|
|
158
|
-
|
|
159
|
-
**vs. [OpenSpec](https://github.com/Fission-AI/OpenSpec)** — Similar philosophy, broader tool support. TracerKit trades breadth (Claude Code only) for depth — native skill discovery, subagents for verification, and fewer artifacts.
|
|
160
|
-
|
|
161
|
-
**vs. nothing** — AI coding without specs means vague prompts and lost context between sessions. TracerKit adds structure without ceremony.
|
|
162
|
-
|
|
163
|
-
<details>
|
|
164
|
-
<summary>Full comparison table</summary>
|
|
165
|
-
|
|
166
|
-
| | Spec Kit | Kiro | OpenSpec | TracerKit |
|
|
167
|
-
| ---------------- | ---------------- | -------------------------- | ----------------------- | ---------------------------------- |
|
|
168
|
-
| **What it is** | CLI + extensions | Agentic IDE (VS Code fork) | Slash-command framework | Claude Code skills (pure Markdown) |
|
|
169
|
-
| **Setup** | Python + uv | Dedicated IDE | npm + init | `npx tracerkit init` |
|
|
170
|
-
| **Phases** | 5 | 3 | 3 | 3 (prd, plan, verify) |
|
|
171
|
-
| **Artifacts** | 4 files | 3+ files | 4+ files | 2 files (PRD, plan) |
|
|
172
|
-
| **Verification** | Manual gates | Diff approval | Manual | Automated PASS/NEEDS_WORK |
|
|
173
|
-
| **Tool lock-in** | Any AI assistant | Kiro IDE only | Any AI assistant | Claude Code only |
|
|
174
|
-
| **Runtime deps** | Python + uv | Proprietary IDE | None | None |
|
|
175
|
-
|
|
176
|
-
</details>
|
|
177
|
-
|
|
178
88
|
## Examples
|
|
179
89
|
|
|
180
90
|
<details>
|
|
@@ -262,6 +172,102 @@ AI: Feature Status Dashboard
|
|
|
262
172
|
|
|
263
173
|
</details>
|
|
264
174
|
|
|
175
|
+
## CLI Reference
|
|
176
|
+
|
|
177
|
+
| Command | Description |
|
|
178
|
+
| -------------------------- | ---------------------------------------------- |
|
|
179
|
+
| `tracerkit init` | Install skills to `~/.claude/skills/` |
|
|
180
|
+
| `tracerkit init <path>` | Install skills to a specific project directory |
|
|
181
|
+
| `tracerkit update` | Refresh to latest version, skip modified files |
|
|
182
|
+
| `tracerkit update --force` | Replace modified files with latest versions |
|
|
183
|
+
| `tracerkit uninstall` | Remove TracerKit skills, keep user artifacts |
|
|
184
|
+
| `tracerkit --version` | Print version |
|
|
185
|
+
| `tracerkit --help` | Show help message |
|
|
186
|
+
|
|
187
|
+
All commands default to the home directory. Pass a path to target a specific project.
|
|
188
|
+
|
|
189
|
+
<details>
|
|
190
|
+
<summary>Metadata Lifecycle</summary>
|
|
191
|
+
|
|
192
|
+
Each PRD carries YAML frontmatter that tracks its position in the workflow. The skills update it automatically — you never need to edit it by hand.
|
|
193
|
+
|
|
194
|
+
**Fields:**
|
|
195
|
+
|
|
196
|
+
- `created` — ISO 8601 UTC timestamp, set when the PRD is written
|
|
197
|
+
- `status` — `created` | `in_progress` | `done`
|
|
198
|
+
- `completed` — ISO 8601 UTC timestamp, set when verification passes
|
|
199
|
+
|
|
200
|
+
**How it changes:**
|
|
201
|
+
|
|
202
|
+
| Stage | Skill | Frontmatter |
|
|
203
|
+
| -------- | ------------------- | ---------------------------------------------------- |
|
|
204
|
+
| Defined | `/tk:prd` | `created: 2025-06-15T14:30:00Z`<br>`status: created` |
|
|
205
|
+
| Planning | `/tk:plan` | `status: in_progress` |
|
|
206
|
+
| Verified | `/tk:verify` (PASS) | `status: done`<br>`completed: 2025-06-20T09:00:00Z` |
|
|
207
|
+
|
|
208
|
+
<details>
|
|
209
|
+
<summary>Example frontmatter at each stage</summary>
|
|
210
|
+
|
|
211
|
+
After `/tk:prd`:
|
|
212
|
+
|
|
213
|
+
```yaml
|
|
214
|
+
---
|
|
215
|
+
created: 2025-06-15T14:30:00Z
|
|
216
|
+
status: created
|
|
217
|
+
---
|
|
218
|
+
```
|
|
219
|
+
|
|
220
|
+
After `/tk:plan`:
|
|
221
|
+
|
|
222
|
+
```yaml
|
|
223
|
+
---
|
|
224
|
+
created: 2025-06-15T14:30:00Z
|
|
225
|
+
status: in_progress
|
|
226
|
+
---
|
|
227
|
+
```
|
|
228
|
+
|
|
229
|
+
After `/tk:verify` (PASS):
|
|
230
|
+
|
|
231
|
+
```yaml
|
|
232
|
+
---
|
|
233
|
+
created: 2025-06-15T14:30:00Z
|
|
234
|
+
status: done
|
|
235
|
+
completed: 2025-06-20T09:00:00Z
|
|
236
|
+
---
|
|
237
|
+
```
|
|
238
|
+
|
|
239
|
+
</details>
|
|
240
|
+
|
|
241
|
+
</details>
|
|
242
|
+
|
|
243
|
+
<details>
|
|
244
|
+
<summary>Compared to</summary>
|
|
245
|
+
|
|
246
|
+
**vs. [Spec Kit](https://github.com/github/spec-kit)** (GitHub) — Thorough but heavyweight. 5 phases, Python setup, rigid phase gates. TracerKit is 3 phases, zero deps, automated verification.
|
|
247
|
+
|
|
248
|
+
**vs. [Kiro](https://kiro.dev/)** (AWS) — Powerful but locked to a dedicated IDE. TracerKit works inside Claude Code with pure Markdown skills.
|
|
249
|
+
|
|
250
|
+
**vs. [OpenSpec](https://github.com/Fission-AI/OpenSpec)** — Similar philosophy, broader tool support. TracerKit trades breadth (Claude Code only) for depth — native skill discovery, subagents for verification, and fewer artifacts.
|
|
251
|
+
|
|
252
|
+
**vs. nothing** — AI coding without specs means vague prompts and lost context between sessions. TracerKit adds structure without ceremony.
|
|
253
|
+
|
|
254
|
+
<details>
|
|
255
|
+
<summary>Full comparison table</summary>
|
|
256
|
+
|
|
257
|
+
| | Spec Kit | Kiro | OpenSpec | TracerKit |
|
|
258
|
+
| ---------------- | ---------------- | -------------------------- | ----------------------- | ---------------------------------- |
|
|
259
|
+
| **What it is** | CLI + extensions | Agentic IDE (VS Code fork) | Slash-command framework | Claude Code skills (pure Markdown) |
|
|
260
|
+
| **Setup** | Python + uv | Dedicated IDE | npm + init | `npx tracerkit init` |
|
|
261
|
+
| **Phases** | 5 | 3 | 3 | 3 (prd, plan, verify) |
|
|
262
|
+
| **Artifacts** | 4 files | 3+ files | 4+ files | 2 files (PRD, plan) |
|
|
263
|
+
| **Verification** | Manual gates | Diff approval | Manual | Automated PASS/NEEDS_WORK |
|
|
264
|
+
| **Tool lock-in** | Any AI assistant | Kiro IDE only | Any AI assistant | Claude Code only |
|
|
265
|
+
| **Runtime deps** | Python + uv | Proprietary IDE | None | None |
|
|
266
|
+
|
|
267
|
+
</details>
|
|
268
|
+
|
|
269
|
+
</details>
|
|
270
|
+
|
|
265
271
|
## Contributing
|
|
266
272
|
|
|
267
273
|
1. Fork the repo and create a feature branch
|
package/dist/bin.js
CHANGED
|
@@ -24,13 +24,13 @@ function o(e) {
|
|
|
24
24
|
}
|
|
25
25
|
function s(r) {
|
|
26
26
|
if (r.includes("--help") || r.includes("-h")) return a;
|
|
27
|
-
if (r.includes("--version") || r.includes("-v")) return ["tracerkit/1.3.
|
|
27
|
+
if (r.includes("--version") || r.includes("-v")) return ["tracerkit/1.3.11"];
|
|
28
28
|
let i = r[0], s = r.slice(1);
|
|
29
29
|
switch (i) {
|
|
30
30
|
case "init": return t(o(s));
|
|
31
31
|
case "update": {
|
|
32
32
|
let t = s.includes("--force"), n = e(o(s.filter((e) => e !== "--force")), { force: t });
|
|
33
|
-
return n.push("", "Updated to tracerkit/1.3.
|
|
33
|
+
return n.push("", "Updated to tracerkit/1.3.11"), n.push("If using Claude Code, restart your session to load changes."), n;
|
|
34
34
|
}
|
|
35
35
|
case "uninstall": return n(o(s));
|
|
36
36
|
default: return a;
|