doc-consistency

What problem does it solve?

This Skill prevents documentation drift by ensuring that when code or documented behavior changes, the corresponding docs stay accurate for what users actually experience.

Core Features & Use Cases

• Ask-on-inkling synchronization: triggers doc-update decisions when edits could make sibling docs inaccurate, using an explicit user approval gate rather than silent propagation.
• Bidirectional drift detection: covers both directions—editing docs that describe code and editing code (or metadata/HTML/CSS) that docs describe—then flags possible user-observable mismatches.
• Scoped, cascade-proof updates: updates only the docs the user authorizes, with stop conditions to avoid broad fan-out without fresh confirmation.

Quick Start

Use doc-consistency when you modify a design/spec or when you change implementation files that a spec describes, then ask the Skill to identify which sibling docs might need propagation before updating anything.