docs-writer

To generate technical documentation for Gemini CLI features, describe the feature and a plan-driven process investigates the codebase, drafts Markdown content aligned with the Google Developer Documentation Style Guide, and verifies links for publishing.

Writing a contributor guide for a Gemini CLI repository involves following CONTRIBUTING.md requirements, investigating relevant code for context, and drafting style-compliant Markdown that explains migration notes and feature pages accurately.

Ensuring API reference documentation follows the Google Developer Documentation Style Guide requires drafting content in present tense, validating correctness against repository code, and running formatting checks to prepare Markdown for publishing.

Yes, you can create migration notes for the docs directory by planning the documentation request, investigating the codebase changes, and outputting ready-to-publish Markdown that fulfills project contribution standards.

Generating Markdown documentation does not require manual code investigation because the process reads the relevant repository code automatically to ensure accuracy and context before drafting the feature pages or API references.

Using a style guide for technical writing in a contributing workflow reduces back-and-forth, ensures consistency across feature pages, and guarantees that Markdown output meets the project's specific contribution standards before publishing.