deskwork
What an agent noticed, tracked as real work
An agent that spots a problem mid-task usually mentions it once and moves on. deskwork files it as a GitHub issue, keeps the dependency edges between issues honest, and writes a roadmap into the repository - with the date, the issue count it was built from and one line of reasoning per call, so the ordering can be argued with rather than trusted.
Install deskwork
Add the DBHQ marketplace, once
/plugin marketplace add dbhq-uk/marketplaceInstall the skill
/plugin install deskwork@dbhq
Both commands work in Claude Code and in Codex. The marketplace is a public repository you can read first: dbhq-uk/marketplace (external site)
What it is good at
Filing a finding where it will be seen again
capture turns something an agent noticed into a tracked issue with its context attached, instead of a sentence in a transcript nobody will read twice.
Keeping three different issue identifiers apart
One issue carries an issue number, a REST database id and a GraphQL node id, and none of them is interchangeable. Pass a number where a database id belongs and GitHub returns a success having linked a different issue in a different repository - so all three are distinct types with guards, and every dependency write resolves the number first and reads the edge back afterwards.
Recording why the order is the order
The roadmap carries the date, the issue count behind it and a line of reasoning per call. It is built to be disagreed with, which a generated list of numbers cannot be.
Leaving the reasoning to the agent and the decision to you
review gathers and presents, the agent reasons about the ordering, a human approves, and only then does anything write a dependency edge. Nothing here computes a priority and presents it as a fact.
What it does not do
It does not close issues
There is no close verb anywhere in it. A pull request may carry Closes #N and GitHub closes the issue on merge, after a human has reviewed - so the constraint holds itself rather than depending on restraint.
It does not merge
It may propose a merge order and record the reasoning behind it. A human merges, and nothing here can push to a base branch - which matters most where merging to the default branch is what deploys.
It does not infer a dependency edge
An edge exists because it was proposed and accepted, and the reasoning is recorded beside it. Nothing is derived from titles, labels or timing.
It does not hold a credential
An authenticated GitHub CLI is the credential. Nothing in the repository or in its own settings directory carries a token.
Read it before you install it
Every line is public and MIT licensed. The README is the long version of this page, including the parts that are still rough.