tracerkit 1.18.2 → 1.19.0

package/README.md

@@ -21,7 +21,16 @@ Named after the tracer-bullet technique from _The Pragmatic Programmer_: **Trace
 
 AI assistants work best with small, well-scoped tasks — not sprawling layers or flat task lists. TracerKit structures every feature as **tracer-bullet vertical slices**: each phase cuts through every layer (schema → service → API → UI → tests) and is demoable on its own. Integration problems surface early, not at the end.
 
-Three skills drive the workflow: **define** (`/tk:prd`), **plan** (`/tk:plan`), **verify** (`/tk:check`). The AI reads your specs directly, counts progress, and marks completed work done. Pure Markdown, zero runtime deps.
+Four skills drive the workflow: **define** (`/tk:prd`), **plan** (`/tk:plan`), **build** (`/tk:build`), **verify** (`/tk:check`). The AI reads your specs directly, counts progress, and marks completed work done. Pure Markdown, zero runtime deps.
+
+```
+DEFINE          PLAN           BUILD            VERIFY
+/tk:prd  ───▶  /tk:plan  ───▶  /tk:build  ───▶  /tk:check
+  │               │               │                 │
+  ▼               ▼               ▼                 ▼
+PRD doc       Phased plan    Implement phase    Pass/fail
+                              + feedback loops   + status
+```
 
 ## Get Started
 
@@ -111,7 +120,9 @@ AI:  Phase 1 — Theme visible end-to-end
      Written .tracerkit/plans/dark-mode-support.md
      Run `/tk:check dark-mode-support` when ready?
 
-You: # open the plan, implement each phase, write tests...
+You: /tk:build dark-mode-support
+AI:  Phase 1 — Theme visible end-to-end (3 remaining)
+     Implementing... all checks pass. Commit?
 
 You: /tk:check dark-mode-support
 AI:  Status: done | Total: 5/5
@@ -158,6 +169,7 @@ Direction is inferred from the current `storage` config. All artifacts are migra
 | ------------------ | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------- |
 | `/tk:prd <idea>`   | Interview → codebase scan → structured PRD             | `.tracerkit/prds/<slug>.md` or GitHub Issue                                                     |
 | `/tk:plan <slug>`  | PRD → phased vertical slices, each demoable on its own | `.tracerkit/plans/<slug>.md` or GitHub Issue                                                    |
+| `/tk:build <slug>` | Implement next incomplete phase, run feedback loops    | Code changes + checked items in plan                                                            |
 | `/tk:brief`        | Feature dashboard with progress and suggested focus    | Terminal only, no files                                                                         |
 | `/tk:check [slug]` | Verify done-when checkboxes against codebase and tests | Verdict block in plan. On `done`: status updated (local) or issues closed + PRs linked (GitHub) |
 

package/dist/bin.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { a as e, f as t, i as n, l as r, n as i, o as a, p as o, r as s, s as c, t as l, u } from "./uninstall-CNw_7khV.js";
+import { a as e, f as t, i as n, l as r, n as i, o as a, p as o, r as s, s as c, t as l, u } from "./uninstall-CNGQ7MEU.js";
 import { existsSync as d, readFileSync as f, statSync as p } from "node:fs";
 import { dirname as m, join as h, resolve as g } from "node:path";
 import { fileURLToPath as _ } from "node:url";

package/dist/index.js

@@ -1,2 +1,2 @@
-import { c as e, i as t, n, o as r, r as i, t as a, u as o } from "./uninstall-CNw_7khV.js";
+import { c as e, i as t, n, o as r, r as i, t as a, u as o } from "./uninstall-CNGQ7MEU.js";
 export { r as COMMANDS, e as DEPRECATED_SKILLS, o as SKILL_NAMES, i as init, n as migrateStorage, a as uninstall, t as update };

package/dist/{uninstall-CNw_7khV.js → uninstall-CNGQ7MEU.js}

@@ -71,6 +71,7 @@ var C = [
 	"tk:brief",
 	"tk:prd",
 	"tk:plan",
+	"tk:build",
 	"tk:check"
 ], w = ["tk:verify"], T = {
 	force: "--force",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "tracerkit",
-  "version": "1.18.2",
-  "description": "Spec-driven workflow for AI coding agents — PRD → plan → verify. Pure Markdown skills, zero runtime deps.",
+  "version": "1.19.0",
+  "description": "Spec-driven workflow for AI coding agents — PRD → plan → build → verify. Pure Markdown skills, zero runtime deps.",
   "license": "MIT",
   "author": {
     "name": "helderberto",

package/skills/brief/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Session briefing — shows active features, progress, and suggested focus. Use at the start of a session to orient.
+description: Session briefing — shows active features, progress, and suggested focus. Use at the start of a session, when asking what to work on, or when checking active features.
 ---
 
 **Config**: read `.tracerkit/config.json` (default: `local`). Follow matching `<!-- if:local/github -->` blocks.

package/skills/build/SKILL.md

@@ -0,0 +1,192 @@
+---
+description: Implement one phase of a plan. Reads plan, finds next incomplete phase, implements it, runs feedback loops, marks checkboxes, offers commit. One phase per invocation. Use when the user wants to implement, code, build, or work on the next phase of a plan.
+argument-hint: '[slug]'
+---
+
+**Config**: read `.tracerkit/config.json` (default: `local`). Follow matching `<!-- if:local/github -->` blocks.
+
+# Build Phase
+
+Implement the next incomplete phase of a plan — one phase per invocation.
+
+**Context window**: recommend `/clear` before starting to maximize token budget.
+
+**Interactive prompts**: present options as a numbered list and wait for the user's choice.
+
+## Pre-loaded context
+
+<!-- if:local -->
+
+- Available plans: !`ls .tracerkit/plans/*.md 2>/dev/null || echo "(none)"`
+  <!-- end:local -->
+  <!-- if:github -->
+- Available plans: list open GitHub Issues with label `{{github.labels.plan}}`
+<!-- end:github -->
+
+## Input
+
+The argument (if provided) is: $ARGUMENTS
+
+Use argument as `<slug>`. If empty, list available plans and ask the user to select one.
+
+Accepts slug or `@file` reference:
+
+```
+/tk:build dark-mode-support
+/tk:build @.tracerkit/plans/dark-mode-support.md
+```
+
+If argument starts with `@`, treat it as a file path — read that file directly as the plan.
+
+## Workflow
+
+### 1. Load the plan
+
+<!-- if:local -->
+
+Read `.tracerkit/plans/<slug>.md`. If missing, list plans and ask the user to select one.
+
+<!-- end:local -->
+<!-- if:github -->
+
+Find plan issue: open issue with label `{{github.labels.plan}}`, title matching `[{{github.labels.plan}}] <slug>:`. If missing, list plans and ask the user to select one.
+
+<!-- end:github -->
+
+### 2. Find the next incomplete phase
+
+Scan the plan for `## Phase N` headings. For each phase, count `- [ ]` and `- [x]` checkboxes.
+
+The **next incomplete phase** is the first phase that has at least one unchecked `- [ ]` item.
+
+If all phases are complete (zero unchecked items across all phases):
+
+> All phases complete. Run `/tk:check <slug>` to verify.
+
+Stop here.
+
+### 3. Present the phase
+
+Show the phase title and its unchecked items:
+
+```
+Phase N — <title> (M remaining)
+- [ ] First unchecked item
+- [ ] Second unchecked item
+```
+
+### 4. Offer a feature branch
+
+If on the default branch (main/master), ask:
+
+> Create branch `feat/<slug>`?
+>
+> 1. Yes, create branch (Recommended)
+> 2. No, stay on current branch
+
+If accepted, create and switch to the branch.
+
+If already on a feature branch, skip this step.
+
+### 5. Implement the phase
+
+Work through each unchecked item in order. For each item:
+
+1. Read the plan's architectural decisions and the current item's context
+2. Explore relevant code to understand existing patterns and conventions
+3. Implement the change — follow the project's conventions (CLAUDE.md, linter config, test setup)
+4. Write tests alongside implementation (follow the project's existing test patterns)
+
+**Do not** impose coding rules, style, or conventions. Follow what the project already uses.
+
+**Do not** implement items from other phases. Stay within the current phase boundary.
+
+### 6. Run feedback loops
+
+After implementing the phase, detect and run available project scripts. Check `package.json` for these scripts (run only what exists):
+
+| Script pattern                     | Purpose       |
+| ---------------------------------- | ------------- |
+| `typecheck`, `tsc`, `type-check`   | Type checking |
+| `test`, `vitest`, `jest`           | Tests         |
+| `lint`, `eslint`                   | Linting       |
+| `format:check`, `prettier --check` | Formatting    |
+
+Run each detected script. If any fails:
+
+1. Read the error output
+2. Fix the issue
+3. Re-run the failing script
+4. Repeat until all pass (max 3 attempts per script)
+
+If a script still fails after 3 attempts, treat it as a **blocker** — pause and ask the user for help:
+
+> **Blocker**: `<script>` fails after 3 attempts.
+> Last error: `<error summary>`
+>
+> How to proceed?
+>
+> 1. I'll fix it — pause and wait
+> 2. Skip this check and continue
+> 3. Abort this phase
+
+Wait for the user's response before continuing.
+
+### 7. Mark checkboxes
+
+After all feedback loops pass, update checkboxes in the plan file:
+
+<!-- if:local -->
+
+For each completed item, change `- [ ]` → `- [x]` in `.tracerkit/plans/<slug>.md`.
+
+<!-- end:local -->
+<!-- if:github -->
+
+For each completed item, change `- [ ]` → `- [x]` in the plan issue body using `gh issue edit`.
+
+<!-- end:github -->
+
+### 8. Offer commit
+
+Present the changes and ask:
+
+> Phase N complete — all checks pass. Commit?
+>
+> 1. Yes, commit
+> 2. No, I'll review first
+
+If the user chooses to commit:
+
+1. Stage the implementation files (not `.tracerkit/` artifacts unless the project dogfoods TracerKit)
+2. Create a commit with a message following the project's commit conventions
+3. Confirm: "Committed. Run `/tk:build <slug>` for Phase N+1, or `/tk:check <slug>` to verify."
+
+If the user chooses to review:
+
+> Ready for review. Run `/tk:build <slug>` again when ready to continue.
+
+### 9. Blockers during implementation
+
+If implementation requires something the agent cannot provide (API key, external service, manual setup, design decision):
+
+> **Blocker**: <description of what's needed>
+>
+> How to proceed?
+>
+> 1. I've resolved it — continue
+> 2. Skip this item for now
+> 3. Abort this phase
+
+Wait for the user's response. Never guess or work around a blocker silently.
+
+## Rules
+
+- **One phase per invocation** — never auto-advance to the next phase
+- **Never modify PRD content** — the PRD is read-only
+- **Never modify plan content** beyond marking checkboxes `[x]`
+- **Never skip a phase** — phases must be completed in order
+- **Never impose conventions** — follow the project's existing setup
+- **HITL at every decision point** — commits, blockers, and branch creation require user approval
+- **Feedback loops are mandatory** — always run available checks before marking items complete
+- **Do not push to remote** — only commit locally

package/skills/plan/SKILL.md

@@ -217,25 +217,11 @@ Carried forward from PRD verbatim.
 Gaps found in the PRD needing resolution. Blank if none.
 ```
 
-Print one line per phase: `Phase N — <title> (<condition summary>)`. Then ask: "What's next?" with options: "Start implementing" (Recommended) / "Run `/tk:check <slug>`" / "Done for now".
+Print one line per phase: `Phase N — <title> (<condition summary>)`. Then ask: "What's next?" with options: "Run `/tk:build <slug>`" (Recommended) / "Run `/tk:check <slug>`" / "Done for now".
 
 ## Execution guidance
 
-When implementing this plan, **always offer to create a feature branch** before writing any code. Ask: "Create branch `feat/<slug>`?" with options: "Yes, create branch" (Recommended) / "No, stay on current branch". If accepted, create the branch from the default branch.
-
-### During implementation
-
-Mark each "Done when" checkbox `[x]` **immediately after verifying** the condition.
-
-Always update the local plan file (`.tracerkit/plans/<slug>.md`): change `- [ ]` → `- [x]`. This file is the working copy for both local and GitHub modes.
-
-<!-- if:github -->
-
-**Sync to GitHub at phase boundaries**: after completing all items in a phase, update the plan issue body with `gh issue edit` to reflect the local state. This avoids per-item API calls.
-
-After all phases, open a PR with body containing `Closes #<prd-issue>, Closes #<plan-issue>`.
-
-<!-- end:github -->
+To implement this plan phase by phase, run `/tk:build <slug>`. It handles branch creation, implementation, feedback loops, checkbox marking, and commits — one phase per invocation.
 
 ## Rules