A planned project stops when an agent ticks the plan itself #246

Closed
opened 2026-10-27 15:30:58 -04:00 by cmoriarty · 1 comment
Owner

What happens
In run 119, the coding agent ticked its own item in PLAN.md. script.update-plan then found nothing to tick, so plan.next was skipped. The project stopped with two items left, and nothing said so.

What we want
Development is iterative, so a project re-plans after every run:

  • Every run ends with a replan and starts the next run, whoever edited the plan.
  • The project ends only when the plan says it's done.
  • If it stops for any other reason, it says so, and why.

Done when
A run whose agent edits PLAN.md still leads to a replan and the next run.

Where to look: _plan_completing in src/osf/engine/conditions.py needs .osf/plan/tick.json, which only script.update-plan writes.

From the Braid vs Claude Code pinball test, 2026-10-27 (runs 110–120).

**What happens** In run 119, the coding agent ticked its own item in `PLAN.md`. `script.update-plan` then found nothing to tick, so `plan.next` was skipped. The project stopped with two items left, and nothing said so. **What we want** Development is iterative, so a project re-plans after every run: - Every run ends with a replan and starts the next run, whoever edited the plan. - The project ends only when the plan says it's done. - If it stops for any other reason, it says so, and why. **Done when** A run whose agent edits `PLAN.md` still leads to a replan and the next run. Where to look: `_plan_completing` in `src/osf/engine/conditions.py` needs `.osf/plan/tick.json`, which only `script.update-plan` writes. _From the Braid vs Claude Code pinball test, 2026-10-27 (runs 110–120)._
Author
Owner

What shipped

  • An item the run's own agent ticked now counts as the run's tick.
  • A run the plan started carries the project on (replan, then the next item) whatever it ticked.
  • When the next item cannot start, the project's page says why.

Test
tests/pipeline/test_plan.py: run 119's case now replans and goes on.

Shipped in 5598ddf (OpenSpec change iterative-planned-projects, archived).

**What shipped** - An item the run's own agent ticked now counts as the run's tick. - A run the plan started carries the project on (replan, then the next item) whatever it ticked. - When the next item cannot start, the project's page says why. **Test** `tests/pipeline/test_plan.py`: run 119's case now replans and goes on. _Shipped in 5598ddf (OpenSpec change `iterative-planned-projects`, archived)._
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#246
No description provided.