agent-bober 0.11.3 → 0.11.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-bober",
-  "version": "0.11.3",
+  "version": "0.11.5",
   "description": "Multi-agent harness for building applications autonomously with any LLM. Researcher, Planner, Curator, Generator, Evaluator pipeline. Supports Claude, GPT, Gemini, Ollama. MCP server for Cursor/Windsurf.",
   "type": "module",
   "main": "dist/index.js",

package/skills/bober.eval/SKILL.md

@@ -189,6 +189,18 @@ Respond with EXACTLY this JSON structure (no other text):
    {"event":"eval-completed","contractId":"...","evalId":"...","result":"pass|fail","timestamp":"..."}
    ```
 
+4. **If `overallResult` is `"pass"`:**
+   - Update the contract: set `status` to `"completed"`, `completedAt` to current ISO-8601 timestamp. Save to `.bober/contracts/<contractId>.json`.
+   - Update `.bober/progress.md` — change the sprint line to `[completed]`.
+   - **Check if the plan is now fully complete.** Read the PlanSpec's `sprints` array to get the total count. Count how many of those contracts now have `status: "completed"`. If ALL sprints are completed (N/N):
+     - Update the PlanSpec: set `status` to `"completed"` and `completedAt` to current ISO-8601 timestamp. Save to `.bober/specs/<specId>.json`. **The `status` field MUST remain in the first 10 lines of the JSON** so future runs can skip it with a partial read.
+     - Update `.bober/progress.md` — change the plan's status line to `completed (N/N sprints)`.
+     - Log event: `{"event":"plan-completed","specId":"...","sprintsCompleted":N,"timestamp":"..."}`
+
+5. **If `overallResult` is `"fail"`:**
+   - Update the contract: set `status` to `"needs-rework"`, `lastEvalId` to the eval ID. Save to `.bober/contracts/<contractId>.json`.
+   - Update `.bober/progress.md` — change the sprint line to `[needs-rework]`.
+
 If the subagent crashed or returned a malformed response, report the error clearly and suggest the user retry.
 
 ## Step 5: Output Report

package/skills/bober.run/SKILL.md

@@ -91,11 +91,17 @@ If it fails, report the missing prerequisites and stop.
 
 ### 1c. Check for Existing Plans
 
-Read `.bober/specs/` and `.bober/progress.md`. If there is an existing plan with incomplete sprints:
+List all spec files in `.bober/specs/`. For each spec, read only the **first 5 lines** of the JSON file. The `status` field is near the top — if it says `"completed"`, skip that spec entirely (do not load its contracts or read further).
 
-- If the user provided a new task description that clearly differs from the existing plan: create a new plan (go to Step 2)
-- If the user provided no task or a task that matches the existing plan: resume from the next incomplete sprint (skip to Step 3)
-- Log your decision but do NOT ask the user — autonomous mode means you decide and move forward.
+Collect only the specs where `status` is NOT `"completed"` (i.e. `"planned"` or `"in-progress"`). These are the **actionable specs**.
+
+- **No actionable specs + user provided a new task:** Create a new plan (go to Step 2).
+- **No actionable specs + no task provided:** Tell the user all plans are complete. Stop.
+- **Exactly one actionable spec:** Resume from its next incomplete sprint (skip to Step 3).
+- **Multiple actionable specs + user provided a task:** Match it to the most relevant actionable spec, or create a new plan if none match.
+- **Multiple actionable specs + no task:** Pick the most recently created actionable spec.
+
+Log your decision but do NOT ask the user — autonomous mode means you decide and move forward.
 
 Log event:
 ```json
@@ -501,13 +507,17 @@ When done, respond with EXACTLY this JSON structure (no other text):
 ### 3g. Process the Evaluation Result
 
 **On PASS:**
-1. Update contract status to `completed` and save to `.bober/contracts/`.
-2. Update `.bober/progress.md`.
+1. Update contract status to `completed`, set `completedAt` to current ISO-8601 timestamp, and save to `.bober/contracts/`.
+2. Update `.bober/progress.md` — change the sprint line to `[completed]`.
 3. Log event:
    ```json
    {"event":"sprint-completed","contractId":"...","specId":"...","iteration":N,"timestamp":"..."}
    ```
-4. Print milestone:
+4. **Check if the plan is now fully complete.** Read the PlanSpec's `sprints` array to get the total sprint count. Count how many of those contracts now have `status: "completed"`. If ALL sprints are completed (N/N):
+   - Update the PlanSpec: set `status` to `"completed"` and `completedAt` to current ISO-8601 timestamp. Save to `.bober/specs/<specId>.json`. **The `status` field MUST remain in the first 10 lines of the JSON** so future runs can skip it with a partial read.
+   - Update `.bober/progress.md` — change the plan's status line to `completed (N/N sprints)`.
+   - Log event: `{"event":"plan-completed","specId":"...","sprintsCompleted":N,"timestamp":"..."}`
+5. Print milestone:
    ```
    === Sprint <N>/<total> PASSED ===
    Title: <title>
@@ -515,7 +525,8 @@ When done, respond with EXACTLY this JSON structure (no other text):
    Progress: [=====>    ] <N>/<total> sprints complete
    Next: <next sprint title>
    ```
-5. Move to next sprint.
+   If all sprints are done, print `=== PLAN COMPLETE ===` instead of "Next:".
+6. Move to next sprint.
 
 **On FAIL with retries remaining:**
 1. Check if iteration < `evaluator.maxIterations` (default: 3).

package/skills/bober.sprint/SKILL.md

@@ -30,13 +30,15 @@ Also read `.bober/principles.md` if it exists. You will include the principles t
 
 ## Step 1: Identify the Target Sprint
 
+**Find the active PlanSpec.** List all specs in `.bober/specs/`. For each spec, read only the **first 5 lines** — the `status` field is near the top. Skip any spec where `status` is `"completed"`. From the remaining specs, pick the most recent one (sort by `createdAt` descending).
+
+If all specs are `completed` and no sprint number was provided, tell the user all plans are complete.
+
 **If a sprint number was provided as an argument:**
-- Load the most recent PlanSpec from `.bober/specs/` (sort by `createdAt` descending)
 - Find the contract for that sprint number: `.bober/contracts/sprint-<specId>-<N>.json`
 - Verify it exists and its status is `proposed`, `in-progress`, or `needs-rework`
 
 **If no sprint number was provided:**
-- Load the most recent PlanSpec
 - Find the first sprint contract with status `proposed` or `needs-rework`
 - If all sprints are `completed`, tell the user all sprints are done
 - If a sprint is `in-progress`, resume it
@@ -362,7 +364,12 @@ Respond with EXACTLY this JSON structure (no other text):
    {"event":"sprint-completed","contractId":"...","specId":"...","iteration":N,"timestamp":"..."}
    ```
 
-4. **Report success to the user:**
+4. **Check if the plan is now fully complete.** Read the PlanSpec's `sprints` array to get the total count. Count how many of those contracts now have `status: "completed"`. If ALL sprints are completed (N/N):
+   - Update the PlanSpec: set `status` to `"completed"` and `completedAt` to current ISO-8601 timestamp. Save to `.bober/specs/<specId>.json`. **The `status` field MUST remain in the first 10 lines of the JSON** so future runs can skip it with a partial read.
+   - Update `.bober/progress.md` — change the plan's status line to `completed (N/N sprints)`.
+   - Log event: `{"event":"plan-completed","specId":"...","sprintsCompleted":N,"timestamp":"..."}`
+
+5. **Report success to the user:**
    ```
    === Sprint <N> PASSED on iteration <M> ===
 
@@ -374,6 +381,7 @@ Respond with EXACTLY this JSON structure (no other text):
 
    Next sprint: <next sprint title> (run /bober-sprint to continue)
    ```
+   If all sprints are done, report `=== PLAN COMPLETE (N/N sprints) ===` instead of "Next sprint".
 
 ### If the sprint FAILS and retries remain: