Skip to content

Commit 11df33c

Browse files
committed
sync skills: plan-todo learns goal_reset, the way out of a paused goal
Regenerated via sync-skills.py. The arm step now says what a pause does and does not allow, and the picking-up-a-sprint step has the model-side exit: goal_reset deletes a stopped row rather than resuming the objective, so an agent that inherits a paused sprint can clear it, arm a new goal, and say so plainly. Session-Id: miraculous-coyote-of-significant-sorcery
1 parent 5bc431b commit 11df33c

1 file changed

Lines changed: 7 additions & 3 deletions

File tree

‎site-src/skills/plan-todo/SKILL.md‎

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,8 @@ not in any agent's head — agents get compacted, files don't.
4646
without them, and that `/goal pause` stops it while `/goal` shows where it is.
4747
The row is not a notification; a loop the person does not know is running is a
4848
loop they cannot stop. `goal_start` leaves an already-active goal alone and
49-
refuses to lift a pause — the brake is the user's, not yours.
49+
refuses to lift a pause — the brake is the user's, not yours (`goal_reset` is
50+
the way past a pause: it deletes the row instead of resuming it).
5051
6. **Work the PLAN, top uncompleted item first.** When you finish an item:
5152
- Verify it against its stated criteria (build, test, live eyeball — whatever
5253
the item says). No criteria were written? The repo's test suite is the floor.
@@ -94,5 +95,8 @@ not in any agent's head — agents get compacted, files don't.
9495
`await memory("sql", "select status, objective, turns_used from goals where session_id='<this session id>'")`
9596
(the id is in your system prompt's first line). A sprint nobody is continuing
9697
stalls at the end of the turn, and the last agent's `goal_done`/`goal_blocked`
97-
— or a pause you must NOT lift — is why. Over a stopped goal `goal_start` is a
98-
restart: fresh id, zeroed counters, so say so when you tell the user.
98+
is why. Over a stopped goal `goal_start` is a restart: fresh id, zeroed
99+
counters. A `paused` row is the one thing `goal_start` refuses — the brake is
100+
the user's — and `await goal_reset()` is how out: it DELETES the row rather
101+
than resuming the objective, so say plainly that you cleared the paused goal
102+
and armed a new one.

0 commit comments

Comments
 (0)