tracerkit 1.16.0 → 1.17.1

package/package.json

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

package/skills/check/SKILL.md

@@ -9,6 +9,8 @@ argument-hint: '[slug]'
 
 Check implementation against a plan. Update checks, stamp findings, transition status, and mark complete when done.
 
+**Interactive prompts**: use `AskUserQuestion` when available for selections and confirmations; otherwise present options as a numbered list.
+
 ## Pre-loaded context
 
 <!-- if:local -->
@@ -50,7 +52,7 @@ For each `.md` file in `.tracerkit/prds/`:
 6. If plan issue exists, count progress from checkboxes in its body (see Progress Algorithm below). Show `—` if no plan.
 <!-- end:github -->
 
-Ask which feature to verify.
+Present each feature as an option and let the user pick which to verify. Use `AskUserQuestion` when available; otherwise present as a numbered list.
 
 ## Progress Algorithm
 
@@ -62,12 +64,12 @@ Count `- [x]` and `- [ ]` lines under each `## Phase N` heading. Per-phase: `Pha
 
 <!-- if:local -->
 
-Read `.tracerkit/plans/<slug>.md`. If missing, list plans and ask.
+Read `.tracerkit/plans/<slug>.md`. If missing, list plans and ask the user to select one (use `AskUserQuestion` when available).
 
 <!-- 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.
+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 (use `AskUserQuestion` when available).
 
 <!-- end:github -->
 

package/skills/plan/SKILL.md

@@ -9,6 +9,8 @@ argument-hint: '[slug]'
 
 Break a PRD into phased vertical slices (tracer bullets).
 
+**Interactive prompts**: use `AskUserQuestion` when available for selections, confirmations, and approval steps; otherwise present options as a numbered list.
+
 <!-- if:local -->
 
 Output: `.tracerkit/plans/<slug>.md`.
@@ -34,7 +36,7 @@ Output: a GitHub Issue with label `{{github.labels.plan}}`.
 
 The argument (if provided) is: $ARGUMENTS
 
-Use argument as `<slug>`. If empty, list available PRDs and ask.
+Use argument as `<slug>`. If empty, list available PRDs and ask the user to select one (use `AskUserQuestion` when available; otherwise present as a numbered list).
 
 ## Workflow
 
@@ -42,12 +44,12 @@ Use argument as `<slug>`. If empty, list available PRDs and ask.
 
 <!-- if:local -->
 
-Read `.tracerkit/prds/<slug>.md`. If missing, list PRDs and ask. If `.tracerkit/plans/<slug>.md` exists, ask: overwrite or new name?
+Read `.tracerkit/prds/<slug>.md`. If missing, list PRDs and ask the user to select one. If `.tracerkit/plans/<slug>.md` exists, ask: "Overwrite existing" / "Pick a new name". Use `AskUserQuestion` when available; otherwise present as a numbered list.
 
 <!-- end:local -->
 <!-- if:github -->
 
-Find PRD issue: open issue with label `{{github.labels.prd}}`, title matching `[{{github.labels.prd}}] <slug>:`. If missing, list PRDs and ask. If plan issue with label `{{github.labels.plan}}` and matching title exists, ask: update or new name?
+Find PRD issue: open issue with label `{{github.labels.prd}}`, title matching `[{{github.labels.prd}}] <slug>:`. If missing, list PRDs and ask the user to select one. If plan issue with label `{{github.labels.plan}}` and matching title exists, ask: "Update existing plan" / "Use a new name". Use `AskUserQuestion` when available; otherwise present as a numbered list.
 
 <!-- end:github -->
 
@@ -110,7 +112,7 @@ Each phase: thin vertical slice through all layers (schema → service → API
 
 - 1 module touched → 2–3 phases max
 - 2–3 modules touched → 3–5 phases max
-- 4+ modules or 6+ phases → stop and ask the user to split the PRD
+- 4+ modules or 6+ phases → stop and ask: "PRD touches 4+ modules. Split before planning?" with options: "Split the PRD" (Recommended) / "Continue anyway". Use `AskUserQuestion` when available.
 
 Count "modules touched" by scanning the PRD's New Modules and Schema Changes sections.
 
@@ -122,7 +124,7 @@ Assign an agent tag to tasks where appropriate:
 
 ### 5. Quiz the user
 
-Present breakdown (title, user stories covered, done-when per phase). Ask: granularity right? Merge or split? Iterate until approved.
+Present breakdown (title, user stories covered, done-when per phase). Ask: "How's the granularity?" with options: "Looks good, proceed" (Recommended) / "Merge some phases" / "Split a phase". Use `AskUserQuestion` when available; otherwise present as a numbered list. Iterate until approved.
 
 ### 6. Save plan
 
@@ -215,15 +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: "Run `/tk:check <slug>` when ready?"
+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". Use `AskUserQuestion` when available; otherwise present as a numbered list.
 
 ## Execution guidance
 
-When implementing this plan, **always offer to create a feature branch** before writing any code:
-
-> "Create branch `feat/<slug>` for this work? (Y/n)"
-
-If accepted, create the branch from the default branch.
+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". Use `AskUserQuestion` when available. If accepted, create the branch from the default branch.
 
 ### During implementation
 

package/skills/prd/SKILL.md

@@ -9,6 +9,8 @@ argument-hint: <idea>
 
 Skip satisfied steps. If argument provided, skip to Step 2.
 
+**Interactive prompts**: use `AskUserQuestion` when available for choices, confirmations, and interview questions (structured selection UI); otherwise present options as a numbered list.
+
 ## Pre-loaded context
 
 <!-- if:local -->
@@ -34,12 +36,12 @@ If empty, go to Step 1; derive slug after gathering the idea. If provided, deriv
 
 <!-- if:local -->
 
-Output: `.tracerkit/prds/<slug>.md`. If exists, ask: overwrite or new name?
+Output: `.tracerkit/prds/<slug>.md`. If exists, ask: "Overwrite existing" / "Pick a new name" (use `AskUserQuestion` when available).
 
 <!-- end:local -->
 <!-- if:github -->
 
-Output: GitHub Issue with label `{{github.labels.prd}}`, title `[{{github.labels.prd}}] <slug>: <Feature Title>`. If matching issue exists, ask: update or new slug?
+Output: GitHub Issue with label `{{github.labels.prd}}`, title `[{{github.labels.prd}}] <slug>: <Feature Title>`. If matching issue exists, ask: "Update existing issue" / "Use a new slug" (use `AskUserQuestion` when available).
 
 <!-- end:github -->
 
@@ -57,7 +59,7 @@ Map current state: data models, services, API routes, frontend, tests. Note exis
 
 ### 3. Interview
 
-One question at a time. Lead with your recommended answer. Explore code instead of asking when possible. Offer A/B/C for terse answers.
+One question at a time. Lead with your recommended answer (mark it `(Recommended)` and list first). Explore code instead of asking when possible. Present 2–4 options for each question — structured choices are faster than free-text. Use `AskUserQuestion` when available; otherwise present as a numbered list.
 
 | Branch           | Key questions                           | Skip when                        |
 | ---------------- | --------------------------------------- | -------------------------------- |
@@ -71,7 +73,7 @@ One question at a time. Lead with your recommended answer. Explore code instead
 
 ### 3b. Gray areas
 
-Surface ambiguities, contradictions, unstated assumptions. Present numbered list. Resolve all before continuing.
+Surface ambiguities, contradictions, unstated assumptions. For each gray area, present proposed resolution options (use `AskUserQuestion` when available). Resolve all before continuing.
 
 ### 4. Design modules
 
@@ -79,7 +81,7 @@ Sketch modules. Favor **deep modules** — simple interface (1-3 entry points) h
 
 Shallow signals: many small 1:1 functions, callers compose multiple calls, feature changes require interface changes.
 
-Present modules. Confirm which need tests.
+Present modules. Confirm which need tests (multiSelect). Use `AskUserQuestion` when available; otherwise present as a checklist for the user to confirm.
 
 ### 5. Write PRD
 
@@ -134,4 +136,4 @@ PRD body structure (same for local file and issue body). Omit empty sections. No
 
 ---
 
-Then ask: "Run `/tk:plan <slug>` next?"
+Then ask: "What's next?" with options: "Run `/tk:plan <slug>`" (Recommended) / "Done for now". Use `AskUserQuestion` when available; otherwise present as a numbered list.