Select the correct documentation workflow (authoring vs planning vs handoff) and enforce portability and verifiability.
When to use
Use this skill when you need to:
Write or update developer-facing documentation
Create a repeatable dev-docs bundle for a task
Update dev-docs for handoff, context recovery, or archival
Operating mode (governor)
Select exactly one workflow below.
After selecting, invoke the chosen workflow skill and follow it end-to-end.
Routing (pick one)
If you need...
Use this workflow skill
Author or update developer documentation (guides, APIs, runbooks)
author-developer-documentation
Create a new dev-docs task bundle (overview/plan/architecture/notes/verification)
create-dev-docs-plan
Update an existing dev-docs bundle for handoff or archive
update-dev-docs-for-handoff
Shared non-negotiables
Progressive disclosure
Keep top-level docs short; move deep detail into supporting files under dev-docs/ or the selected workflow skill’s supporting folders (reference, examples, templates) when present.
No secrets
Do not include credentials, tokens, or internal-only URLs.
Actionable verification
Every doc set must include concrete verification steps (commands/checks + expected results).
Steps
Identify whether the intent is: (a) write docs, (b) start a dev task bundle, or (c) handoff/update.
Select exactly one workflow from the routing table.
State the selection explicitly.
Invoke the selected workflow skill and execute it end-to-end.
Verification
Exactly one workflow was selected and executed
Outputs use progressive disclosure (examples/templates for long content)
Verification steps are concrete and reproducible
No secrets or sensitive URLs were included
Boundaries
MUST NOT mix multiple documentation workflows in the same execution pass
MUST NOT include secrets/credentials/tokens in documentation
MUST NOT publish unverifiable instructions
Included assets
None (router only).
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: willyu1007-skill-template-addon-docs3description: Docs (workflow router)4---56# Docs (workflow router)78## Purpose9Select the correct documentation workflow (authoring vs planning vs handoff) and enforce portability and verifiability.1011## When to use12Use this skill when you need to:13- Write or update developer-facing documentation14- Create a repeatable dev-docs bundle for a task15- Update dev-docs for handoff, context recovery, or archival1617## Operating mode (governor)18- Select **exactly one** workflow below.19- After selecting, invoke the chosen workflow skill and follow it end-to-end.2021## Routing (pick one)2223| If you need... | Use this workflow skill |24|---|---|25| Author or update developer documentation (guides, APIs, runbooks) | `author-developer-documentation` |26| Create a new dev-docs task bundle (overview/plan/architecture/notes/verification) | `create-dev-docs-plan` |27| Update an existing dev-docs bundle for handoff or archive | `update-dev-docs-for-handoff` |2829## Shared non-negotiables301) **Progressive disclosure**31 - Keep top-level docs short; move deep detail into supporting files under `dev-docs/` or the selected workflow skill’s supporting folders (reference, examples, templates) when present.32332) **No secrets**34 - Do not include credentials, tokens, or internal-only URLs.35363) **Actionable verification**37 - Every doc set must include concrete verification steps (commands/checks + expected results).3839## Steps401. Identify whether the intent is: (a) write docs, (b) start a dev task bundle, or (c) handoff/update.412. Select exactly one workflow from the routing table.423. State the selection explicitly.434. Invoke the selected workflow skill and execute it end-to-end.4445## Verification46- [ ] Exactly one workflow was selected and executed47- [ ] Outputs use progressive disclosure (examples/templates for long content)48- [ ] Verification steps are concrete and reproducible49- [ ] No secrets or sensitive URLs were included5051## Boundaries52- MUST NOT mix multiple documentation workflows in the same execution pass53- MUST NOT include secrets/credentials/tokens in documentation54- MUST NOT publish unverifiable instructions5556## Included assets57- None (router only).5859---60> Converted and distributed by [TomeVault](https://tomevault.io/claim/willyu1007) — claim your Tome and manage your conversions.61<!-- tomevault:4.0:skill_md:2026-04-14 -->
Run npx skillmds@latest add tomevault-io/willyu1007-skill-template-addon-docs 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.
Docs (workflow router) It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
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.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.