# documentation_engineer

documentation_engineer — a Claude Code subagent that writes documentation from supplied code, interfaces, and requirements. It turns a documentation request and source material into a task-focused Markdown document.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/documentation_engineer.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/agenticorglab-documentation-engineer

## What it does

The subagent drafts documentation from code, interfaces, and requirements supplied with the request. It uses the requested audience, purpose, scope, and format to shape the document.

The result is a complete Markdown document with a title, audience, prerequisites, and scope. It can also cover procedures, examples, limitations, errors, and verification steps. Examples are distinguished from verified behavior and recommendations.

It must not fabricate APIs, commands, options, or file paths. The task needs a documentation request and source context, such as APIs, code, schemas, or existing docs.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/documentation_engineer.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/documentation_engineer.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/documentation_engineer.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/documentation_engineer.md

## When to use it
- document an API from its code and schemas
- write a procedure for a defined audience
- separate verified behavior from examples and recommendations
- describe limitations and verification steps

## Example prompts
- Write an API guide for developers using this code and its schemas.
- Create a Markdown setup procedure and list its prerequisites.
- Document this interface's limitations and explain how to verify the result.

## Similar
- [documentation-engineer](https://affpapa.org/en/nevibecode/agents/documentation-engineer.md) — subagent · 735 installs
- [code-documentation-tutorial-engineer](https://affpapa.org/en/nevibecode/agents/code-documentation-tutorial-engineer.md) — subagent · ★ 42780 repo stars
- [documentation-expert](https://affpapa.org/en/nevibecode/agents/documentation-expert.md) — subagent · 6992 installs
- [documentation-and-adrs](https://affpapa.org/en/nevibecode/skills/documentation-and-adrs.md) — skill · 80700 installs
- [golang-documentation](https://affpapa.org/en/nevibecode/skills/golang-documentation.md) — skill · 42700 installs
- [documentation-writer](https://affpapa.org/en/nevibecode/skills/documentation-writer.md) — skill · 27757 installs

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
