mirror of
https://github.com/jparkerweb/plan2code.git
synced 2026-11-18 21:01:19 -08:00
Add Stop with a handoff, handoff chips on the dashboard, and a one-step delete for fixed bugs
AI Assisted
This commit is contained in:
1 parent
33a0dbd34a
commit
36843e4bc9
34 files changed
+1926
-267
No files matched your search
@@ -47,7 +47,7 @@ first, and post before anything slow.
|
||||
|
||||
## What the page already knows
|
||||
|
||||
`state.scan` is `{ hasAgents, isGit, pending, specs: [{ dir, name, state, detail, touched }] }`,
|
||||
`state.scan` is `{ hasAgents, isGit, pending, specs: [{ dir, name, state, detail, touched }], handoffs, handoffsDir }`,
|
||||
a snapshot of the last `open` (a spec created mid-session appears the next time
|
||||
the session resumes as a dashboard). `pending` is how many files a commit would
|
||||
take (`null` when git cannot say): the Git card never greys out, shows the count
|
||||
@@ -64,6 +64,34 @@ person's turn by itself.
|
||||
A `__stop` before a pick ends the session the usual way: `finish` (paused
|
||||
headline, `"command": "/plan2code"`) then `stop` (`console-stop.md`).
|
||||
|
||||
`handoffs` is this checkout's unused handoffs, newest first (`[{ id, title,
|
||||
next, written, spec, skill, workflow }]`, read from `~/.plan2code/handoffs/`
|
||||
by `open`, a dashboard only), and `handoffsDir` is that folder. The picker shows
|
||||
them as dashed **Handoff** chips after the specs.
|
||||
|
||||
## A pick-up
|
||||
|
||||
Selecting a handoff chip shows a preview and hides the skill cards. **Pick it up
|
||||
here** sends a hop like a launch, naming only the id:
|
||||
|
||||
```jsonc
|
||||
{ "type": "submit",
|
||||
"actions": [{ "i": "__pickup", "type": "pickup", "handoff": "2026-10-17-1152-handoff" }],
|
||||
"reply": "Pick up the handoff \"Lunch vote\" right here in this session.",
|
||||
"resume": "node \"…/console.mjs\" open --resume <sid> --no-open --workflow quick-task --spec specs/lunch-vote",
|
||||
"skillFile": "…/plan2code-quick-task/SKILL.md",
|
||||
"handoffFile": "~/.plan2code/handoffs/2026-10-17-1152-handoff.md" }
|
||||
```
|
||||
|
||||
`wait` has already read the handoff's stored skill and spec, marked the handoff
|
||||
used (the next scan no longer lists it) and put the command in `resume`. Run
|
||||
`resume`, read `skillFile` with your file-read tool, then read `handoffFile`,
|
||||
follow the skill from where its real work starts, and carry on from the
|
||||
handoff's **Next task**. When the send carries `"fallback": true` the named
|
||||
skill or spec was gone, or the Handoff skill wrote it: say so in one line,
|
||||
since Quick Task is picking it up.
|
||||
The handoff's document stays on disk until the 30-day sweep.
|
||||
|
||||
## A delete
|
||||
|
||||
The ✕ on a picker chip, after the page's two-step confirm (what goes, then
|
||||
@@ -78,3 +106,8 @@ having touched nothing, and drops the workspace remembered for that spec.
|
||||
Then `open --resume <sid> --no-open --workflow dashboard` to rescan, and post
|
||||
the menu again with `--wait`, its note saying what went or why it did not.
|
||||
The page shows the chip as "Deleting…" until that rescan lands.
|
||||
|
||||
A handoff's **Delete** sends the same `__delete`, with `handoff` (its id) where a
|
||||
spec has `spec`. Delete it through
|
||||
`node "<CONSOLE>" delete-handoff --handoff <id>` (exit 3 with `message` when it
|
||||
refuses, nothing touched), then rescan and post the menu as for a spec.
|
||||
Reference in new issue
Block a user