workbench-work-items
Work item management for Workbench CLI. Use when creating, updating, linking, or closing work items and tracking execution status.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Key settings
-
.workbench/config.json: paths.itemsDir, paths.doneDir, ids.width, prefixes, git.branchPattern. - Status values: draft, ready, in-progress, blocked, done, dropped.
Core workflows
- Ensure planning artifacts exist (specs, ADRs, architecture docs) before major work.
- Create a work item and set its initial status.
- Link related specs, ADRs, files, PRs, or issues.
- Update status and close work items when done.
Commands
Create a task:
workbench.ps1 item new --type task --title "Do the thing" --status draft --priority medium --owner platform
Update status:
workbench.ps1 item status TASK-0001 in-progress --note "started implementation"
Close and move to done:
workbench.ps1 item close TASK-0001 --move
Link docs or PRs:
workbench.ps1 item link TASK-0001 --spec /docs/10-product/spec.md --adr /docs/40-decisions/ADR-YYYY-MM-DD-title.md --pr https://github.com/org/repo/pull/1
Output
- Work items in
work/items(active) andwork/done(closed). - Linked docs and external artifacts tracked in front matter.
Guardrails
- Use a work item for every meaningful change and link the supporting docs.
- Keep status accurate so reports and boards stay reliable.
- If a decision happens during work, update/create the ADR and link it.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!