Docs (workflow router)
Purpose
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
reference/,examples/, andtemplates/.
- •Keep top-level docs short; move deep detail into
- •
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).