Generates and maintains two types of outward-facing documentation: dev guides for integrators and contributors, user guides for end users. It triggers automatically after feature acceptance when interface contracts or user-visible behavior changes, or you can invoke it directly with "write documentation." The workflow pulls from spec docs but filters out implementation details and internal design notes, keeping only what the target audience needs. Outputs land in docs/dev/ and docs/user/ with YAML frontmatter tracking status (draft, current, outdated). The interesting bit is how it enforces separation: specs live in .codestable/ and describe what was built and why, while guides are task-oriented and publishable. If you've got a codebase where specs and user docs keep drifting or bleeding into each other, this creates a clear boundary.
npx skills add https://github.com/liuzhengdongfortest/codestable --skill cs-guide