What problem does it solve? Code changes often leave documentation stale or inconsistent. This Skill defines the invariant core of a technical-writer role that is the single agent allowed to write into docs/, keeping documentation synchronized with code changes in the same task. ## Core Features & Use Cases - Fixed documentation pipeline: context loading, edits, humanizer pass, markdownlint and link validation, index updates, and a structured report. - Four operating modes: code-change (sync docs after code edits), review (consistency audit without edits), validate (linters only), and new-doc creation from templates. - Strict style and NEVER rules: YAML frontmatter on every article, kebab-case naming, clickable file links, no AI-marker words, no credentials in examples, and no editing of code or running tests. - Use Case: After a backend agent changes an API endpoint, the wrapper skill invokes this core to update the affected docs pages, re-render related diagrams, run the humanizer, validate links and frontmatter, and return a structured report to the teamlead. ## Quick Start Import this core from a project wrapper by adding a line stating that the techwriter-core SKILL.md applies, then invoke the techwriter role with a mode such as code-change or review.
