How do I install the Workbench Docs skill?

Run npx skillmds@latest add majiayu000/workbench-docs-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Workbench Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workbench Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workbench Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Workbench Docs?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workbench Docs by majiayu000 — Agent Skill

Name: Workbench Docs
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Key settings

.workbench/config.json: paths.docsRoot, paths.templatesDir, ids.width, prefixes, git.defaultBaseBranch, github.owner, github.repository.
Use workbench config show --format json to 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:

workbench doc new --type doc --title "Title" --path docs/10-product/title.md --work-item TASK-0001

Create a spec:

workbench doc new --type spec --title "Title" --path docs/10-product/title.md --work-item TASK-0001

Create an architecture doc:

workbench doc new --type doc --title "System design" --path docs/20-architecture/system-design.md --work-item TASK-0001

Create an ADR:

workbench 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:

workbench doc link --type spec --path docs/10-product/title.md --work-item TASK-0001

Unlink a doc from work items:

workbench doc unlink --type adr --path docs/40-decisions/ADR-YYYY-MM-DD-title.md --work-item TASK-0001

Sync front matter and backlinks:

workbench doc sync --all --dry-run
workbench doc sync --all

Summarize doc changes:

workbench 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-item or workbench item link.
For major changes, write a spec before implementation.
When decisions change, update or create the ADR.
Prefer workbench doc commands; workbench spec and workbench adr are deprecated.

---name: workbench-docs-2description: Documentation workflows for Workbench CLI. Use when creating or updating specs, ADRs, runbooks, guides, or general docs, and when syncing backlinks or change notes.---## Key settings- `.workbench/config.json`: paths.docsRoot, paths.templatesDir, ids.width, prefixes, git.defaultBaseBranch, github.owner, github.repository.- Use `workbench config show --format json` to verify effective settings.## Core workflows1. Planning phase: create specs and architecture docs before major changes.2. Doing phase: keep docs updated as implementation decisions change.3. Keep doc front matter and backlinks in sync.4. Summarize doc changes when publishing.## CommandsCreate a doc:```bashworkbench doc new --type doc --title "Title" --path docs/10-product/title.md --work-item TASK-0001```Create a spec:```bashworkbench doc new --type spec --title "Title" --path docs/10-product/title.md --work-item TASK-0001```Create an architecture doc:```bashworkbench doc new --type doc --title "System design" --path docs/20-architecture/system-design.md --work-item TASK-0001```Create an ADR:```bashworkbench 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:```bashworkbench doc link --type spec --path docs/10-product/title.md --work-item TASK-0001```Unlink a doc from work items:```bashworkbench doc unlink --type adr --path docs/40-decisions/ADR-YYYY-MM-DD-title.md --work-item TASK-0001```Sync front matter and backlinks:```bashworkbench doc sync --all --dry-runworkbench doc sync --all```Summarize doc changes:```bashworkbench 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-item` or `workbench item link`.- For major changes, write a spec before implementation.- When decisions change, update or create the ADR.- Prefer `workbench doc` commands; `workbench spec` and `workbench adr` are deprecated.

Frequently asked questions

Workbench Docs