@jwilger/pi-development-system 0.67.0 → 0.68.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jwilger/pi-development-system",
-  "version": "0.67.0",
+  "version": "0.68.0",
   "description": "A pi extension package representing a seasoned approach to software development using a full AI SDLC.",
   "keywords": [
     "pi-package"

package/prompts/devsys-plan.md

@@ -8,5 +8,5 @@ Write the plan for the current work with the work-intake-and-slicing skill.
 2. Write `docs/plan/<slug>.md` with these sections: Goal and why; Constraints (what must not change); Increments, each shippable on its own and small enough to release, each with an **Acceptance** list (observable checks that say the increment is done) and a final Release step (commit, push, CI green, publish, update) followed by a STOP for the user; for every task a task record whose header is `## <id> — <title>` and whose sections are written exactly as `**Goal:**`, `**Files:**`, `**Interfaces:**`, `**First failing test:**`, `**Steps:**`, `**Run:**`, `**Expected:**`, `**Out of scope:**` (label and colon inside the bold, one section per label); a Progress checklist with one box per increment.
 3. Write each task so that someone who sees only that task could finish it. Never write `TBD`.
 4. Run `devsys_task_check` on every task record you wrote and fix each one until it says ready. Split any that come back too-big.
-5. If a `create_goal` tool exists in this session, call it with the objective "complete docs/plan/<slug>.md honouring its Constraints and Progress checklist, one increment at a time, stopping after each increment's Release step". Otherwise tell the user the plan path so they can start a goal on it. Do not depend on any goal tool's file format.
-6. Stop and ask the user to review the plan before any implementation starts.
+5. Stop and ask the user to review the plan before any implementation starts. Do not start a goal yet: a goal tool may continue on its own and begin implementing before the review.
+6. Only after the user approves the plan: if a `create_goal` tool exists in this session, call it with the objective "complete docs/plan/<slug>.md honouring its Constraints and Progress checklist, one increment at a time, stopping after each increment's Release step". Otherwise tell the user the plan path so they can start a goal on it. Do not depend on any goal tool's file format.

package/src/planning/task-check-tool.ts

@@ -29,6 +29,15 @@ const insideRepo = (cwd: string, target: string): boolean => {
   return rel !== "" && !rel.startsWith("..") && !isAbsolute(rel);
 };
 
+/** Jev's aspect keys, named as the record's own sections so the author knows what to edit. */
+const SECTION_OF: Readonly<Record<string, string>> = {
+  goal: "Goal",
+  interfaces: "Interfaces",
+  firstFailingTest: "First failing test",
+  steps: "Steps",
+  check: "Run and Expected",
+};
+
 /** `devsys_task_check`: structural readiness is deterministic; Jev adds "specific enough" and "one task". */
 export function createTaskCheckTool(deps: {
   jev: (ctx: ExtensionContext) => Jev;
@@ -72,7 +81,8 @@ export function createTaskCheckTool(deps: {
           `${record.id}: too-big. Split it into task records that each need one failing test, then check each.`,
         );
       }
-      return reply(`${record.id}: needs-detail. Make these more specific: ${missing.join(", ")}.`);
+      const named = missing.map((m) => SECTION_OF[m] ?? m).join(", ");
+      return reply(`${record.id}: needs-detail. Make these more specific: ${named}.`);
     },
   };
 }