Document

When to Use

• User wants documentation committed in the repo (create, update, or prune)—not a chat-only walkthrough
• User asks to document a feature, module, command, API, release, operational procedure, or existing doc scope
• User wants README, architecture, API, devops, runbook, migration, or colocated package docs refreshed after code changes
• Triggers: "document this", "update the README", "write a runbook", "add docs for", "document the API", "capture how X works in the repo", /document

User clarifications (Cursor)

When you need a discrete decision with a small set of clear options (about 2–6)—for example audience, doc location, or scope—prefer the AskQuestion tool so the user gets structured choices. Ask one decision at a time when this skill sequences questions that way.

If AskQuestion is unavailable in the current environment, ask the same choices in ordinary chat (same options, same ordering).

Use plain chat (not forced multiple-choice) when the answer is inherently free-form—for example pasted existing doc text, a custom doc layout, or an open-ended description of what to cover.

Scope