deskworklisted

# deskwork - turn what an agent notices into tracked work File side issues without stopping the task, record what blocks what with a reason, and keep a `roadmap.md` in git that says what comes next and why. ## When not to use - Not for Jira or Confluence. Use `atlassian`. - Not for Trello. Use `trello`. - Not in a repository that has not opted in. Say so and stop; offer `init`. - Not to close, delete, assign or prioritise an issue. deskwork never does any of these. ## Start here ```bash python3 "${CLAUDE_SKILL_DIR}/scripts/deskwork.py" doctor ``` | Exit | Means | Do | |---|---|---| | 0 | Done, or no drift | Carry on | | 1 | Refused, or drift found | Read the message; `init` or `intake` fixes most drift | | 2 | Not opted in | Say so and stop. Offer `init` | | 3 | The config file is wrong | Show the message | | 4 | Written, and not as asked | Stop. Do not retry: the message names what exists | | 10 | `capture` found possible duplicates | Read them, then comment or re-run with `--file` | Run it from anywhere in the repository, a worktree included. Issues go to the repository the `origin` remote points at. ## capture - file an issue ```bash python3 "${CLAUDE_SKILL_DIR}/scripts/deskwork.py" capture --template --type Bug > body.md python3 "${CLAUDE_SKILL_DIR}/scripts/deskwork.py" capture --title "Retry logic drops the last attempt" --type Bug --area infra --body-file body.md ``` 1. Read the files, tests and recent commits first, and cite them in the body. 2. Fill every se