Key settings
- •
.workbench/config.json: paths.docsRoot, paths.templatesDir, ids.width, prefixes, git.defaultBaseBranch, github.owner, github.repository. - •Use
workbench.ps1 config show --format jsonto verify effective settings.
Core workflows
- •Planning phase: create specs and architecture docs before major changes.
- •Doing phase: keep docs updated as implementation decisions change.
- •Keep doc front matter and backlinks in sync.
- •Summarize doc changes when publishing.
Commands
Create a doc:
bash
workbench.ps1 doc new --type doc --title "Title" --path docs/10-product/title.md --work-item TASK-0001
Create a spec:
bash
workbench.ps1 doc new --type spec --title "Title" --path docs/10-product/title.md --work-item TASK-0001
Create an architecture doc:
bash
workbench.ps1 doc new --type doc --title "System design" --path docs/20-architecture/system-design.md --work-item TASK-0001
Create an ADR:
bash
workbench.ps1 doc new --type adr --title "Decision" --path docs/40-decisions/ADR-YYYY-MM-DD-title.md --work-item TASK-0001
Link a doc to work items:
bash
workbench.ps1 doc link --type spec --path docs/10-product/title.md --work-item TASK-0001
Unlink a doc from work items:
bash
workbench.ps1 doc unlink --type adr --path docs/40-decisions/ADR-YYYY-MM-DD-title.md --work-item TASK-0001
Sync front matter and backlinks:
bash
workbench.ps1 doc sync --all --dry-run workbench.ps1 doc sync --all
Summarize doc changes:
bash
workbench.ps1 doc summarize --staged --update-index
Output
- •Markdown docs with Workbench front matter and backlinks.
- •Updated work item references in docs and work items.
Guardrails
- •Keep doc types aligned with folder intent (product, architecture, decisions, runbooks).
- •Always link docs to relevant work items with
--work-itemorworkbench.ps1 item link. - •For major changes, write a spec before implementation.
- •When decisions change, update or create the ADR.
- •Prefer
workbench.ps1 doccommands;workbench.ps1 specandworkbench.ps1 adrare deprecated.