/docs
DocsUser-invoked

Document shipped surfaces so a new integrator can follow them without Slack. Verify examples against real code — not PRDs, not feature work.

When to use

After a public API, MCP, or CLI ships, or when docs have drifted from the code.

Prerequisites

  • A shipped public surface (API, MCP, CLI) or docs that drifted from code.

How to use

  1. Invoke /docs with the audience and doc type (tutorial, API reference, migration).
  2. Point at the real code or MCP paths the examples must match.
  3. Review the draft against a fresh integrator path — no Slack required.
  4. Publish to the agreed docs path; optionally add an /e2e how-to if journeys matter.

Done when

Verified developer docs exist for the surface and examples match real code.

Pipeline

Upstream
/dev (shipped seam) or an existing schema/MCP
Downstream
Published docs path / optional /e2e how-to

Boundaries

Does not write product requirements (/reqs). Does not implement features (/dev). Does not write marketing copy.

Sample prompt

prompt
/docs

Tutorial: wire Cursor to the kit MCP and search Knowledge (intent: incident)

Agent

PRINCIPAL TECH LEAD

Owns: API reference, tutorials, integration guides, migration notes

Use the techlead to [task]
techlead
← Skill catalog