create-doc

To create an onboarding guide, the agent reads repository files and configurations to generate a structured Markdown file covering setup, tests, and deployment. It selects a canonical destination like the docs/ directory and prompts you for any missing details to ensure accuracy.

Documenting architecture decisions is best handled by generating an Architecture Decision Record (ADR). The agent grounds its output by reading repository files and PRs, then authors a structured Markdown file in your docs/ directory while surfacing open questions and assumptions.

To write a postmortem document, the agent captures event details from your conversation or repository sources and creates a timestamped Markdown file in a canonical location. It prompts for missing incident details to ensure a complete and structured record.

Yes, you can update an existing runbook. The agent identifies the document job, checks existing docs/ locations and repository conventions, and updates the current Markdown file with required sections rather than creating a duplicate, while reporting any gaps or assumptions.

Generating API documentation relies on reading existing repository context and references to avoid guessing. You need repository files, existing docs, PRs, or tickets as input sources so the agent can ground the Markdown output and accurately prompt for missing details.