What problem does it solve? Writing or updating technical documentation often produces unverified claims, scope creep, and pages that miss the reader's actual need. This Skill grounds every documentation change in repository evidence, keeps edits bounded to the authorized scope, and validates the result with the project's own checks. ## Core Features & Use Cases - Evidence-grounded writing: Verifies every claim against implementation, tests, CLI help, schemas, or scientific sources before writing, and never invents interfaces, commands, or citations. - Diátaxis-based structuring: Shapes each page around a dominant reader need (tutorial, how-to, reference, or explanation) without forcing artificial structure. - Bounded, validated patches: Makes the smallest coherent change, runs proportionate checks such as Sphinx builds, doctests, and Vale, and reports evidence, results, and remaining uncertainties. - Use Case: A user asks to document a new CLI option. The Skill reads the implementation and CLI help, writes a precise reference section, updates navigation only if needed, builds the docs, and reports the pages changed and checks run. ## Quick Start Use $documentation-authoring to document the new configuration option in the getting-started guide and validate the change with the project's doc build.
