What problem does it solve? Keeping a growing docs/ tree consistent is hard: numbering schemes, frontmatter schemas, link discipline, and file-size limits all drift when docs are written ad hoc. This Skill enforces those conventions for every doc write or edit, whether it is a new chapter in a spike or plan, a frontmatter touch-up, or a restructure of an existing document. ## Core Features & Use Cases - Scaffold enforcement: New prefixed top-level docs (spikes, plans, notes) must be created through the yolo new CLI, which assigns numbers, seeds frontmatter, and returns the canonical path; direct writes are blocked by the pre-write-doc hook. - Convention-guided editing: Applies project doc rules such as the ~500-line soft cap, one topic per file, Mermaid diagrams, TypeScript-style types, and file-level-only cross-references (no #anchor fragments). - Validation and handoff: Runs doc-check-links.sh when cross-references change, re-reads edited files, and uses git mv for renames. - Use Case: While executing a plan, you need a new chapter 04-rollout.md inside docs/plans/p018-auth/. The Skill reads sibling chapters for tone, writes the chapter matching local conventions, links it file-level to siblings, and verifies links before reporting back. ## Quick Start Ask the agent to write a new chapter about rollout strategy in the existing plan directory docs/plans/p018-auth following the project doc conventions.
