@staff0rd/assist 0.260.0 → 0.262.0

package/README.md

@@ -257,7 +257,7 @@ When iterating on assist itself: web server changes only need the `assist sessio
 - `assist refine [id] [--once]` - Launch Claude in `/refine` mode to refine a backlog item; prompts for selection when no id given; `--once` exits when the done signal arrives after refinement completes
 - `assist review-comments [number]` - Launch Claude in `/review-comments` mode to process PR review comments (single session, no chaining); when a PR number is supplied, checks out that PR via `gh pr checkout` first
 - `assist signal next [id]` - Write a next signal to chain into `assist next`; when `id` is supplied, the parent launcher runs that backlog item directly
-- `assist signal done` - Write a done signal marking the session's initial task complete; `--once` launch sessions exit when it arrives, plain sessions ignore it
+- `assist signal done [id]` - Write a done signal marking the session's initial task complete; an optional `id` surfaces the backlog item the session created onto its session card; `--once` launch sessions exit when it arrives, plain sessions ignore it
 
 When `commit.pull` is enabled in config, `assist draft`, `assist bug`, `assist refine`, `assist next`, and `assist backlog run` run `git pull --ff-only` before doing anything else; if the pull fails the command aborts. `assist next` pulls once per invocation, not per item in its loop.
 

package/claude/commands/bug.md

@@ -41,15 +41,16 @@ Ask the user if they want to change anything. Iterate until they confirm.
 
 ## Step 5: Save
 
-Once confirmed, add the item via CLI:
+Once confirmed, add the item via CLI and capture the id it prints:
 ```
 assist backlog add --name "Bug title" --type bug --desc "**Repro:**\n1. ...\n\n**Expected:** ...\n\n**Actual:** ..." --ac "criterion 1" --ac "criterion 2" 2>&1
 ```
+Note the created item id from the output — you'll pass it to the done signal below.
 
 Then show the user the item was created and suggest they can run `assist backlog run <id>` to start implementation.
 
-Finally, signal that the bug-filing task is complete:
+Finally, signal that the bug-filing task is complete, passing the created item id:
 ```
-assist signal done 2>&1
+assist signal done <id> 2>&1
 ```
-This lets a wrapping `assist bug --once` session end; in a plain interactive session it has no effect.
+This lets a wrapping `assist bug --once` session end and surfaces the created item id to the session card; in a plain interactive session it has no effect.

package/claude/commands/draft.md

@@ -73,10 +73,11 @@ Ask the user if they want to change anything. Iterate until they confirm.
 
 Once confirmed, create the item and its phases via CLI commands.
 
-First, add the item:
+First, add the item and capture the id it prints:
 ```
 assist backlog add --name "Item name" --type story --desc "Description text" --ac "criterion 1" --ac "criterion 2" 2>&1
 ```
+Note the created item id from the output — you'll pass it to the done signal below.
 
 Then add each phase:
 ```
@@ -85,8 +86,8 @@ assist backlog add-phase <id> "Phase name" --task "Task 1" --task "Task 2" --man
 
 Then show the user the item was created and suggest they can run `assist backlog run <id>` to start implementation.
 
-Finally, signal that the drafting task is complete:
+Finally, signal that the drafting task is complete, passing the created item id:
 ```
-assist signal done 2>&1
+assist signal done <id> 2>&1
 ```
-This lets a wrapping `assist draft --once` session end; in a plain interactive session it has no effect.
+This lets a wrapping `assist draft --once` session end and surfaces the created item id to the session card; in a plain interactive session it has no effect.