tracerkit 1.9.5 → 1.9.6
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
CHANGED
|
@@ -23,15 +23,20 @@ Without specs, every AI session starts from scratch. Vague prompts, duplicated c
|
|
|
23
23
|
|
|
24
24
|
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.
|
|
25
25
|
|
|
26
|
+
**Deterministic CLI, intelligent skills.** The CLI produces structured, repeatable output — feature tables, progress counts, archive operations — while the skills layer AI reasoning on top. The foundation is deterministic, so every session starts from the same ground truth. AI adds the judgment: interviewing you for scope, designing modules, verifying implementation against specs.
|
|
27
|
+
|
|
26
28
|
## Get Started
|
|
27
29
|
|
|
28
30
|
### Install
|
|
29
31
|
|
|
30
32
|
```bash
|
|
31
|
-
|
|
33
|
+
npm install -g tracerkit
|
|
34
|
+
tracerkit init
|
|
32
35
|
```
|
|
33
36
|
|
|
34
|
-
|
|
37
|
+
The global install is by design — skills call `tracerkit brief`, `tracerkit progress`, and `tracerkit archive` directly to get deterministic output before the AI acts on it. Having the CLI in your PATH keeps this seamless.
|
|
38
|
+
|
|
39
|
+
Skills are installed to `~/.claude/skills/`, available in every project. Safe to re-run — adds missing skills without overwriting ones you've modified.
|
|
35
40
|
|
|
36
41
|
### Workflow
|
|
37
42
|
|
|
@@ -81,7 +86,7 @@ npx tracerkit uninstall . # remove project-scoped skills
|
|
|
81
86
|
|
|
82
87
|
## Skills
|
|
83
88
|
|
|
84
|
-
TracerKit ships
|
|
89
|
+
TracerKit ships skills that take a feature from idea to verified archive.
|
|
85
90
|
|
|
86
91
|
### `/tk:prd <idea>`: Write a PRD
|
|
87
92
|
|
package/package.json
CHANGED
|
@@ -8,30 +8,22 @@ Get a quick overview of all active features, their progress, and what to focus o
|
|
|
8
8
|
|
|
9
9
|
## Pre-loaded context
|
|
10
10
|
|
|
11
|
-
- Briefing: !`
|
|
11
|
+
- Briefing: !`tracerkit brief 2>&1`
|
|
12
12
|
|
|
13
13
|
## Workflow
|
|
14
14
|
|
|
15
15
|
### 1. Present the briefing
|
|
16
16
|
|
|
17
|
-
Display the output above as-is.
|
|
17
|
+
Display the output above as-is. Features with `status: done` are excluded (already archived).
|
|
18
18
|
|
|
19
|
-
|
|
20
|
-
- **Status**: from PRD frontmatter (`created`, `in_progress`) — `unknown` if no frontmatter
|
|
21
|
-
- **Age**: time since `created` date
|
|
22
|
-
- **Progress**: checked/total from plan checkboxes, or `—` if no plan
|
|
23
|
-
- **Next**: first unchecked item from the plan, or `—`
|
|
24
|
-
|
|
25
|
-
Features with `status: done` are excluded (already archived).
|
|
26
|
-
|
|
27
|
-
### 2. Focus recommendation
|
|
19
|
+
### 3. Focus recommendation
|
|
28
20
|
|
|
29
21
|
The **Focus** line at the bottom suggests which feature to work on:
|
|
30
22
|
|
|
31
23
|
- If exactly 1 feature is `in_progress`, it's auto-selected
|
|
32
24
|
- Otherwise, the oldest feature by `created` date is selected
|
|
33
25
|
|
|
34
|
-
###
|
|
26
|
+
### 4. Offer next steps
|
|
35
27
|
|
|
36
28
|
Ask the user what they'd like to do:
|
|
37
29
|
|
|
@@ -9,7 +9,7 @@ Check implementation against a plan. Update checks, stamp findings, transition s
|
|
|
9
9
|
|
|
10
10
|
## Pre-loaded context
|
|
11
11
|
|
|
12
|
-
- Available plans: !`ls {{paths.plans}}/ 2
|
|
12
|
+
- Available plans: !`ls {{paths.plans}}/ 2>&1`
|
|
13
13
|
|
|
14
14
|
## Input
|
|
15
15
|
|
|
@@ -27,7 +27,7 @@ If no argument is provided, scan `{{paths.prds}}/` and `{{paths.plans}}/` and sh
|
|
|
27
27
|
|
|
28
28
|
- **Feature**: slug (filename without `.md`)
|
|
29
29
|
- **Status**: from PRD frontmatter (`created`, `in_progress`, `done`) — `unknown` if no frontmatter
|
|
30
|
-
- **Progress**: run `
|
|
30
|
+
- **Progress**: run `tracerkit progress <slug>` for each feature with a plan — use the Total line (e.g. "3/7"). Show `—` if no plan.
|
|
31
31
|
|
|
32
32
|
After the table, ask which feature to verify.
|
|
33
33
|
|
|
@@ -75,7 +75,7 @@ Based on checks and findings, decide the status transition:
|
|
|
75
75
|
|
|
76
76
|
### 5. Report to user
|
|
77
77
|
|
|
78
|
-
Run `
|
|
78
|
+
Run `tracerkit progress <slug>` to get exact per-phase progress, then print the verdict report:
|
|
79
79
|
|
|
80
80
|
```
|
|
81
81
|
## Verification: <slug>
|
|
@@ -114,7 +114,7 @@ If a previous verdict block exists, replace it with the new one.
|
|
|
114
114
|
If all checks pass and zero BLOCKERS, run:
|
|
115
115
|
|
|
116
116
|
```
|
|
117
|
-
|
|
117
|
+
tracerkit archive <slug>
|
|
118
118
|
```
|
|
119
119
|
|
|
120
120
|
This handles: PRD frontmatter update (`status: done`, `completed` timestamp), file moves to `{{paths.archives}}/<slug>/`, and archived block on the plan.
|
|
@@ -9,7 +9,7 @@ Break a PRD into phased vertical slices (tracer bullets). Output: `{{paths.plans
|
|
|
9
9
|
|
|
10
10
|
## Pre-loaded context
|
|
11
11
|
|
|
12
|
-
- Available PRDs: !`ls {{paths.prds}}/ 2
|
|
12
|
+
- Available PRDs: !`ls {{paths.prds}}/ 2>&1`
|
|
13
13
|
|
|
14
14
|
## Input
|
|
15
15
|
|