Docs

Documentation Orchestration

When this skill is invoked, run the following pipeline:

Step 1: Architecture Audit

Spawn the {{roster.architectAgent}} agent with this prompt:

Audit the current codebase for any changes since the docs were last updated. Read the existing machine docs ({{docs.machineDocSet}}) and compare against the actual project. Produce a concise change report covering:

{{docs.auditChecklist}}

Output ONLY the change report as structured text. Do NOT modify any files.

Step 2: Agent Documentation

Take the change report and spawn the docs-agent agent with this prompt:

Here is the architecture change report for the {{project.name}} codebase:

{step-1 output}

Update the machine docs — {{docs.machineDocSet}} — to reflect the current state of the project. Read the actual source files to verify details — do not rely solely on the change report. Follow the docs-agent skill guidelines for format and structure.

Step 3: Human Documentation

After docs-agent completes, spawn the docs-human agent with this prompt:

The machine docs have just been updated. Update the human-facing documentation — {{docs.humanDocSet}} — to match.

Read the updated machine docs and the actual source to ensure accuracy. Follow the docs-human skill guidelines for format, structure, and its guardrails (owner-voiced docs are flagged, never rewritten).

Important

• Each step must complete before the next begins — the output of each informs the next.
• Step 1 is read-only — the audit agent only reports.
• docs-agent and docs-human SHOULD modify their respective documentation files.