| name | backlog-workflow |
| description | Backlog.md task lifecycle for doro-cli. Use when creating, updating, or finalising tasks so the correct CLI commands, statuses, and branch conventions are followed. |
Backlog Workflow (doro-cli)
Task lifecycle
To Do → In Progress → Done
Commands
npx backlog task list
npx backlog task view <id>
npx backlog task create -t "<title>" \
--description "<desc>"
npx backlog task edit <id> \
--status "In Progress" -a @agent
npx backlog task edit <id> \
--status "Done"
Rules
- Search first — run
npx backlog task list and grep for keywords before creating a task.
- One task per feature — never bundle unrelated work.
- Branch naming —
tasks/<task-id>-<short-slug> (e.g. tasks/DORO-42-dark-mode).
- Link branch — Always add the related branch name to the task description or comments when creating/updating the task.
- Commit format —
DORO-<id>: Title of the task.
- Never commit to
main — create the branch before any code changes.
- Backlog auto-commit is disabled — stage and commit
.backlog/ changes yourself.
- Assign yourself — always pass
-a @agent when setting In Progress.