tracerkit 1.4.6 → 1.4.7

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.
Files changed (2) hide show
  1. package/README.md +19 -17
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -10,21 +10,21 @@
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
+ Named after the tracer-bullet technique from _The Pragmatic Programmer_ — **Tracer** + **Kit**.
14
+
13
15
  **Zero runtime dependencies.** Pure Markdown skills, no build step.
14
16
 
15
17
  </div>
16
18
 
17
19
  ## Why TracerKit?
18
20
 
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.
21
+ Without specs, every AI session starts from scratch — vague prompts, duplicated context, no way to confirm "done." Most planning tools produce flat task lists where nothing works until everything is done.
22
22
 
23
- The term comes from The Pragmatic Programmer. The name **TracerKit** = Tracer (bullet) + Kit.
23
+ TracerKit takes a different approach: **tracer-bullet vertical slices**. 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.
24
24
 
25
25
  ## Get Started
26
26
 
27
- ### 1. Install TracerKit
27
+ ### Install
28
28
 
29
29
  ```bash
30
30
  npx tracerkit init
@@ -32,7 +32,7 @@ npx tracerkit init
32
32
 
33
33
  Skills are installed globally to `~/.claude/skills/`, available in every project. No per-project setup needed.
34
34
 
35
- ### 2. Use the workflow
35
+ ### Workflow
36
36
 
37
37
  ```
38
38
  You: /tk:prd add dark mode support
@@ -65,13 +65,15 @@ npx tracerkit uninstall . # remove project-scoped skills
65
65
 
66
66
  ## Skills
67
67
 
68
+ TracerKit ships four skills — three for the core workflow, one for visibility.
69
+
68
70
  ### Core skills
69
71
 
70
- The three-step workflow that takes a feature from idea to verified archive.
72
+ Three steps that take a feature from idea to verified archive.
71
73
 
72
74
  #### `/tk:prd <idea>`: Write a PRD
73
75
 
74
- Interactive interview to define a feature. Explores the codebase, asks scoping questions one at a time, designs deep modules, and writes a structured PRD.
76
+ Interactive interview that explores your codebase, asks scoping questions one at a time, designs deep modules, and writes a structured PRD.
75
77
 
76
78
  **Output:** `.tracerkit/prds/<slug>.md`
77
79
 
@@ -83,13 +85,13 @@ Reads a PRD and breaks it into phased **tracer-bullet vertical slices**. Each ph
83
85
 
84
86
  #### `/tk:verify <slug>`: Verify and archive
85
87
 
86
- Read-only review that compares the codebase against the plan's done-when conditions. Runs tests, checks user stories, and stamps a **✅ PASS** or **🚧 NEEDS_WORK** verdict. On ✅ PASS, automatically archives the PRD and plan to `.tracerkit/archives/<slug>/`.
88
+ Read-only review that checks the codebase against the plan's done-when conditions. Runs tests, validates user stories, and stamps a **✅ PASS** or **🚧 NEEDS_WORK** verdict. On ✅ PASS, archives the PRD and plan to `.tracerkit/archives/<slug>/` automatically.
87
89
 
88
90
  **Output:** Verdict block in `.tracerkit/plans/<slug>.md`. On ✅ PASS: `.tracerkit/archives/<slug>/prd.md` + `.tracerkit/archives/<slug>/plan.md`
89
91
 
90
92
  ### Helper skills
91
93
 
92
- Useful but optional. This category will grow over time.
94
+ Useful but optional.
93
95
 
94
96
  #### `/tk:status`: Workflow dashboard
95
97
 
@@ -97,13 +99,13 @@ Scans `.tracerkit/prds/` and prints a table of all features grouped by status (`
97
99
 
98
100
  ## Docs
99
101
 
100
- | Document | Description |
101
- | ------------------------------------------------ | --------------------------------------------------- |
102
- | [Examples](docs/examples.md) | End-to-end usage walkthroughs |
103
- | [CLI Reference](docs/cli-reference.md) | All CLI commands and flags |
104
- | [Configuration](docs/configuration.md) | Custom artifact paths via `config.json` |
105
- | [Metadata Lifecycle](docs/metadata-lifecycle.md) | YAML frontmatter states and transitions |
106
- | [Compared to](docs/compared-to.md) | How TracerKit differs from Spec Kit, Kiro, OpenSpec |
102
+ | Document | Description |
103
+ | ------------------------------------------------ | -------------------------------------------------- |
104
+ | [Examples](docs/examples.md) | Walk through end-to-end usage scenarios |
105
+ | [CLI Reference](docs/cli-reference.md) | Browse all CLI commands and flags |
106
+ | [Configuration](docs/configuration.md) | Configure custom artifact paths via `config.json` |
107
+ | [Metadata Lifecycle](docs/metadata-lifecycle.md) | Understand YAML frontmatter states and transitions |
108
+ | [Compared to](docs/compared-to.md) | Compare TracerKit to Spec Kit, Kiro, and OpenSpec |
107
109
 
108
110
  ## Contributing
109
111
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tracerkit",
3
- "version": "1.4.6",
3
+ "version": "1.4.7",
4
4
  "description": "Spec-driven workflow for Claude Code: replace ad-hoc prompts with PRD → plan → verify.",
5
5
  "license": "MIT",
6
6
  "author": {