Doc

Write or update the documentation the caller needs, grounded in the current repository and its accepted intent. A small explanation needs no interview, coverage ledger or separate report. Select only the mode relevant to the task.

Modes

Need	Scope and reference
Explain an API, command, code-map or architecture	Inspect its consumers and source; use code/API guidance or architecture guidance when useful.
Create or improve a README	Lead with the user's problem and a working first-use path; preserve useful depth. See README craft.
Audit or scaffold OSS documentation	Compare existing docs with the requested pack. Create missing files; revise existing files only within the authorized request. See OSS pack.
Initialize missing entry documents	Create only explicitly requested missing files; report existing paths as skipped. See setup examples.
Preserve a session for another context	Write the compact factual handoff described below to the caller's authorized destination.

These are optional task shapes, not successive phases. Detailed references supply techniques and formats; they do not add interviews, approval checkpoints, reports or files beyond the accepted request. Existing authorization to revise specified documents is sufficient.