docs-generate

Efficientworkflow

Mission

Identify audience → choose format → generate content → publish. Every doc is audience-targeted.

When to Use

Use when generating API reference documentation, README files, operational runbooks, postmortems, technical guides, or any other documentation artifact.

Triggers: “write documentation”, “generate docs”, “create a README”, “document this API”, “write a runbook”, “document this module”, “postmortem for”, “technical guide”

Orchestration Flow

1. 3× Zero-Cost draft lanes — doc-generator, doc-readme, doc-api run in parallel (GPT-4.1 / GPT-5 mini)
2. Efficient pass — doc-runbook (Claude Haiku 4.5) merges draft outputs and adds operational context
3. Advanced edit — Claude Sonnet 4.6 reviews for accuracy, tone, and audience fit
4. Deliver — audience-targeted markdown artifacts ready for commit

Skills Invoked

• doc-generator Zero-Cost — inline JSDoc/TSDoc
• doc-readme Zero-Cost — structured README
• doc-api Zero-Cost — OpenAPI / Markdown API reference
• doc-runbook Efficient — operational runbook

Chain-to recommendations

• code-review — review documentation quality after generation
• enterprise-strategy — add generated docs to an enterprise documentation library

Example

Request

{
  "request": "Generate complete documentation for the payment-service: README, API reference, and operational runbook"
}

Output

• README.md — contributor and integration guide
• docs/api.md — OpenAPI-compatible reference
• docs/runbook/payment-service.md — startup, shutdown, alert, and escalation sections

Audience Targeting

Audience	Preferred Skills
Developers integrating the API	doc-api
Operators running the service	doc-runbook
New contributors	doc-readme
Code reviewers	doc-generator