docs-design
Docs Design
Documentation-experience design and measurement for any surface someone reads
to learn, integrate, recover, or retrieve — developer docs, end-user help, and
agent-readable docs. Applied before the docs exist (design) or to keep them
honest over time (measure). Provenance lives in skill.json; this file is
runtime routing only.
Produces: a design-doc.md — a concrete proposed structure (source of
truth, renderings, IA, audience paths, acceptance criteria) — or a
measurement-plan.md — signals, thresholds, owners, actions, and release gates.
Boundaries
Do NOT use to AUDIT or debug existing docs (use docs-audit), to design a code package's developer experience — API/SDK/CLI shape, errors, first-run flow (use dx-design), for end-user visual UI design (use ux-audit), or repo agent hardening (use harden-repo-for-coding-agents), or agent-native docs — AGENTS.md, llms.txt (use agent-docs).