workingon

Bridge between this session and the ticketing tool. A local ledger, filled in by hooks, records what was asked, which files were touched, which commits landed and which notable commands ran.

WO = node ${CLAUDE_PLUGIN_ROOT}/src/bin/workingon.mjs. Every command accepts --json.

Rules

• Record, do not redo. The work is already done; this only documents it.
• One ticket per task, not per session. Work continuing the linked ticket becomes a comment. A different topic becomes a new ticket.
• Never invent anything that is not in the ledger or in the conversation.
• Write in the user's language.
• End the turn with one short line: ticket reference and URL. Nothing else.

The workspace may be shared

Colleagues may be looking at these boards.

• Never create projects, boards or repositories, and never touch tickets this tool did not create.
• Never delete anything. delete exists for the person to run, not for you. If asked to delete, show what would go and wait for explicit confirmation.
• Only write to the destination that ledger resolves. If it says UNDECIDED, ask first. Never pick a destination that merely looks right.
• If create or comment answer [SIMULATED], nothing was written. Say exactly that, without implying a ticket exists.

Default flow

1. Read the state.

WO ledger --session ${CLAUDE_SESSION_ID}

Returns the folder, branch, destination, linked ticket and the work not recorded yet. If the destination is UNDECIDED, go to Undecided folder.

2. Decide.

• Linked ticket and the work continues it: progress comment (step 3b).
• Linked ticket but this is a different topic: new ticket (step 3a).
• No linked ticket: search before creating.

  WO find "keywords" --session ${CLAUDE_SESSION_ID}
  

  If one is clearly the same thing, link it with WO link --issue <id> --session ${CLAUDE_SESSION_ID} --keep-unsynced and go to 3b. Otherwise create.

3a. Create.

WO create --session ${CLAUDE_SESSION_ID} --title "Title" --body-file - <<'END'
<markdown body>
END