Prompt file imported from jlaws/dotfiles (.codex/prompts/j-docs.md). Fill in {{arguments}} before use. Copyright stays with the author.

Before starting, gather diagnostic context:

Detect documentation tooling from config files (docusaurus.config.js, mkdocs.yml, .readthedocs.yml, typedoc.json, sphinx conf.py).
Identify existing docs by searching for docs/, README.md, CHANGELOG.md, or API specification files.
Check for API schemas by searching for openapi.yaml, swagger.json, or GraphQL schema files.
Get scope overview of the target area (if {{arguments}} specifies a component, scope to that; otherwise scan for documentation directories).

For deep documentation guidance, delegate to the documentation-writer agent, passing the diagnostic findings above and the request. It loads its skills (post-ship-doc-sync, output-completeness) and the .agents/references/documentation/ library, then returns specific guidance. Verify its output before presenting.

Help with: {{arguments}}

Before starting, gather diagnostic context: 1. **Detect documentation tooling** from config files (docusaurus.config.js, mkdocs.yml, .readthedocs.yml, typedoc.json, sphinx conf.py). 2. **Identify existing docs** by searching for docs/, README.md, CHANGELOG.md, or API specification files. 3. **Check for API schemas** by searching for openapi.yaml, swagger.json, or GraphQL schema files. 4. **Get scope overview** of the target area (if {{arguments}} specifies a component, scope to that; otherwise scan for documentation directories). For deep documentation guidance, delegate to the `documentation-writer` agent, passing the diagnostic findings above and the request. It loads its skills (post-ship-doc-sync, output-completeness) and the `.agents/references/documentation/` library, then returns specific guidance. Verify its output before presenting. Help with: {{arguments}}

j-docs

About

Use it

Manifest

Reviews