tracerkit 1.7.0 → 1.7.1
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 +11 -9
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@
|
|
|
10
10
|
|
|
11
11
|
Replace ad-hoc AI prompts with a repeatable spec-driven workflow: from idea to verified, archived code.
|
|
12
12
|
|
|
13
|
-
Named after the tracer-bullet technique from _The Pragmatic Programmer_
|
|
13
|
+
Named after the tracer-bullet technique from _The Pragmatic Programmer_: **Tracer** + **Kit**.
|
|
14
14
|
|
|
15
15
|
**Zero runtime dependencies.** Pure Markdown skills, no build step.
|
|
16
16
|
|
|
@@ -18,7 +18,7 @@ Named after the tracer-bullet technique from _The Pragmatic Programmer_ — **Tr
|
|
|
18
18
|
|
|
19
19
|
## Why TracerKit?
|
|
20
20
|
|
|
21
|
-
Without specs, every AI session starts from scratch
|
|
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
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
|
|
|
@@ -36,17 +36,19 @@ Skills are installed globally to `~/.claude/skills/`, available in every project
|
|
|
36
36
|
|
|
37
37
|
```
|
|
38
38
|
You: /tk:prd add dark mode support
|
|
39
|
-
AI:
|
|
39
|
+
AI: Written .tracerkit/prds/dark-mode-support.md
|
|
40
|
+
Run `/tk:plan dark-mode-support` next?
|
|
40
41
|
|
|
41
42
|
You: /tk:plan dark-mode-support
|
|
42
|
-
AI:
|
|
43
|
-
|
|
44
|
-
|
|
43
|
+
AI: Phase 1 — Theme visible end-to-end
|
|
44
|
+
Phase 2 — User can toggle and persist preference
|
|
45
|
+
Written .tracerkit/plans/dark-mode-support.md
|
|
46
|
+
Run `/tk:check dark-mode-support` when ready?
|
|
45
47
|
|
|
46
|
-
You: # implement each phase...
|
|
48
|
+
You: # open the plan, implement each phase, write tests...
|
|
47
49
|
|
|
48
50
|
You: /tk:check dark-mode-support
|
|
49
|
-
AI:
|
|
51
|
+
AI: Status: done | Total: 5/5
|
|
50
52
|
Archived to .tracerkit/archives/dark-mode-support/
|
|
51
53
|
```
|
|
52
54
|
|
|
@@ -97,7 +99,7 @@ Without arguments, shows a feature dashboard with status and progress before ask
|
|
|
97
99
|
| [CLI Reference](docs/cli-reference.md) | Browse all CLI commands and flags |
|
|
98
100
|
| [Configuration](docs/configuration.md) | Configure custom artifact paths via `config.json` |
|
|
99
101
|
| [Metadata Lifecycle](docs/metadata-lifecycle.md) | Understand YAML frontmatter states and transitions |
|
|
100
|
-
| [
|
|
102
|
+
| [Comparison](docs/comparison.md) | Compare TracerKit to Spec Kit, Kiro, and OpenSpec |
|
|
101
103
|
|
|
102
104
|
## Contributing
|
|
103
105
|
|