doc-consistency

To prevent documentation drift, an explicit approval gate prompts you before propagating updates to sibling design or decisions docs. This ensures spec sync with user-observable behavior changes without silent cascades.

Bidirectional drift detection flags user-observable mismatches in both directions: editing docs that describe code, and editing implementation files that docs describe. It identifies which sibling docs need propagation before updating anything.

Yes, doc-consistency applies to synchronized maintenance across sibling docs and implementation files including metadata.json, HTML, CSS, and JavaScript. It works in any workflow with spec-first review.

The best way to keep specs and code aligned is using an ask-on-inkling synchronization policy that prompts for doc-update decisions when edits risk making sibling docs inaccurate. Updates are scoped with stop conditions to prevent uncontrolled cascades.

Yes, YAML frontmatter-driven discovery behavior is required. It enables the inkling-threshold policy that asks the user before propagating updates to avoid silent drift and uncontrolled cascades.

You should avoid silent automated doc propagation when edits could trigger broad fan-out. Doc-consistency uses scoped, cascade-proof updates with explicit stop conditions to prevent uncontrolled cascades without fresh user confirmation.