archflow-agent-doc-writer

Delegate to the doc-writer role, which analyzes the codebase and writes docs/api-reference.md covering endpoints, HTTP methods, parameters, authentication, error codes, and code examples. It links back to the API contract rather than restating schemas.

It creates docs/api-reference.md for the human-facing API guide, docs/ONBOARDING_GUIDE.md for developer setup, and README.md at the repository root. All output goes to a docs subfolder except the README.

No. The API contract is owned exclusively by the api-contract-architect role. The doc-writer documents the layer around it, such as getting-started guides and examples, and reports disagreements between contract and code instead of documenting around them.

It marks anything it could not verify as UNVERIFIED rather than asserting it works. This applies to untested setup steps, ambiguous requirements, or claims that cannot be confirmed against the codebase.

It is an on-demand role, since no Archflow phase currently dispatches it automatically. You invoke it explicitly when a phase or skill delegates documentation work to this role.