What problem does it solve? Teams often let documentation drift out of sync with code and tests, leaving specs stale, contracts ambiguous, and shipped behavior undocumented. This Skill enforces a documentation-first change loop where accepted behavior is written down, implemented, verified, and reconciled in the same change. ## Core Features & Use Cases - Authority mapping by fact type: Assigns each fact to a single canonical owner, such as schemas for exact shapes, focused specs for behavior, and ADRs for rationale. - Bounded change loop: Guides inspection, delta documentation, minimal implementation, contract verification, and drift reconciliation with a closure receipt. - Drift resolution: Provides a structured process for handling disagreements between docs, code, tests, and machine artifacts without defaulting to the newest prose. - Use Case: When adding idempotency keys to an existing payments API, use this Skill to update the OpenAPI schema and API guide first, implement against the documented contract, map tests to acceptance criteria, and close the loop without creating a generic PLAN.md. ## Quick Start Use document-driven development to add a bounded feature contract for this change, then implement and verify it against the documented acceptance criteria.
