Skip to content

oliverjueguen/workingon-claude-skill / skill

workingon

Verified

Record the work done in this Claude Code session in the configured ticketing tool (Jira, Linear, GitHub Issues, Trello or Vikunja), creating the ticket, adding a short progress comment, linking an existing one or closing it. Use it when the [workingon] hook reports unrecorded work, when the user types /workingon, and when they ask to log, track or file what they are working on.

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 {{WORKINGON}}. 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

3b. Comment.

WO comment --session ${CLAUDE_SESSION_ID} --file - <<'END'
<markdown comment>
END

Both mark the ledger as recorded. Do not run WO synced afterwards.

If the heredoc is awkward, write the text to a temporary file and pass its path.

4. Ask whether it is finished.

Only when the session had a ticket linked from the start, and only after the comment or the ticket is written. One question, in the user's language:

¿Doy la tarea por acabada?

  • Yes → WO update --session ${CLAUDE_SESSION_ID} --done
  • No → nothing more. The ticket stays where it is.

Ask, do not decide. Whether something is finished is a judgement about intent, not about the diff: tests can pass on work that is half of what the person meant. A ticket closed early is worse than one left open, because nobody looks at closed tickets again.

Ask once, at the end, and accept the answer. Do not ask again in the same session if the answer was no.

Commits carry the ticket

Where WO githook has been run, commits made while a ticket is linked get a Ticket: <url> trailer, and the log can be read against the board with git log --format='%s | %(trailers:key=Ticket,valueonly)'.

It is a git hook rather than something inside this tool on purpose: it stamps the commits the person makes by hand too, and a scheme that only works when a machine is driving is a scheme with a hole in it.

Never write the trailer into a commit message yourself. If it is missing, the hook is not installed in that repository; say so and offer WO githook.

The board moves itself

WO link drags the card into the "in progress" column, and WO update --done lands it in the done column. Neither needs a separate command and neither should get one: on Vikunja the second is the server's own doing, because a kanban view with a done bucket moves the card as soon as the task is marked done.

So never move cards by hand, and never tell the person to. If a card did not move, link says why on its second line, and the reason is always the same kind: no kanban view, no single column that means "in progress", or a provider without columns. Report that line as it is rather than working around it.

How to write the ticket

Title: what it achieves, not what was touched. One line under 80 characters, no prefixes.

  • Good: Migrate session auth to JWT
  • Bad: Changes in auth.ts and login.tsx, Work on 12 March

Body: five lines at most. One sentence of context and up to four bullets.

<One sentence: what this achieves.>

- <change>
- <change>

Pending: <one line, only if something is left>

Leave out file listings, design rationale, conversation recaps, notes sections and test counts. All of that already lives in the code and in git, and in a ticket it only gets in the way.

Progress comment: two lines. What moved and what is left. Nothing already in the ticket.

Limits are 600 characters for a body and 400 for a comment, enforced by create, update and comment. If a command rejects your text, summarise it. Do not reach for --long.

Arguments

ArgumentAction
(empty)The default flow above.
new <topic>Force a new ticket on that topic, without searching.
<free text>Default flow, using that text as the main topic of the title.
done / closeWO update --session ${CLAUDE_SESSION_ID} --done. Add a closing comment first if work is unrecorded.
link <id>WO link --issue <id> --session ${CLAUDE_SESSION_ID} --keep-unsynced, then comment the pending progress.
unlinkWO unlink --session ${CLAUDE_SESSION_ID}. The exact undo of link: unlinks and sends the card back to the first column. A ticket already done is left alone. To keep the card in progress, do not unlink.
githookWO githook. Installs a prepare-commit-msg hook in this repository so commits carry Ticket: <url> while a ticket is linked. Once per repository. --remove undoes it.
statusWO status --session ${CLAUDE_SESSION_ID}, summarise in two lines. Do not write.
doctorWO doctor. If something fails, explain the concrete fix. Do not write.
setupSee Setting up.
skip / ignoreWO synced --session ${CLAUDE_SESSION_ID}. Drops the pending work without recording it.

Undecided folder

Each folder is decided once. Until then nothing is written, and the hook says so.

Ask with AskUserQuestion, one question, these options:

  • Record it in the default destination, naming it.
  • Record it somewhere else. If chosen, show WO containers and ask which.
  • Do not record anything from this folder, it is private.

Always save the answer so the question is not repeated:

WO config --map <folder>=<container id>     record there
WO config --exclude <folder>                private folder

--exclude also deletes whatever was already captured locally from that folder, and from then on the hooks store nothing about it.

Then continue the normal flow, or say in one line that nothing was recorded.

Setting up

WO setup runs three steps and can be driven with flags:

  1. WO setup --step 1 --provider jira|linear|github|trello|vikunja plus that tool's credentials.
  2. WO setup --step 2 --mode ask|autosave|off [--write-style nudge|silent]
  3. WO setup --step 3 --container <id> [--label "Claude"]

Never ask the user to paste a token into the chat. Tell them to run WO setup themselves in the terminal, or to put it in the config file that WO doctor points at. WO providers lists the supported tools and WO doctor says what is missing.

Full API details and error tables in reference.md.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall