What problem does it solve? Writing in-depth developer documentation is slow and error-prone: guides often ship unverified URLs, stale file paths, and paraphrased sources that mislead readers. This Skill produces long-form developer guides on any project topic with a mandatory verification spine, so every cited URL, path, and quoted fact is checked against its source before publication. ## Core Features & Use Cases - Section-library assembly: Builds each guide from twelve documented section intents in references/skeleton.md, choosing, ordering, and blending sections to fit the topic rather than forcing a fixed template. - Five starting archetypes: Offers system-explainer, rule-deep-dive, how-to, concept-explainer, and change-recap shapes as non-binding starting points, selected via a picker table in references/exemplars.md. - Mandatory verification discipline: Requires WebFetch confirmation of every external URL and Read/Grep confirmation of every on-disk path, symbol, and frontmatter field before citing it, with verbatim quoting of primary sources. - Use Case: Ask for a deep-dive on a project convention like a review-bot loop rule, and receive a saved docs/plans/guides/review-bot-loop-discipline.md with verbatim frontmatter quotes, an ASCII flow diagram, a quick-reference card, and cross-references. ## Quick Start Ask the assistant to write a guide on a specific project topic, for example: write a developer guide explaining how the memory recall system works and save it to the docs folder.
