What problem does it solve? Implemented code changes often leave project documentation stale, causing API specs, data models, and setup guides to drift from actual behavior. This Skill identifies which documentation files are affected by a change and updates only those files, keeping docs accurate without wasting tokens on irrelevant context. ## Core Features & Use Cases - Selective Context Loading: Reads only the documentation files relevant to the change type (data model, API, backend, frontend, or OpenSpec workflow) instead of loading everything. - Ecommerce Consistency Validation: Verifies that documentation preserves domain rules such as separating CustomerOrder from SupplierOrder and hiding supplier data from customer-facing APIs. - Structured Update Report: Produces a summary of changed and unchanged documentation plus alignment checks against the data model, API spec, and standards. - Use Case: After adding a new endpoint for return requests, run this Skill to update docs/api-spec.yml and docs/data-model.md while confirming no customer-facing exposure of supplier fields. ## Quick Start Ask the AI to review the recently implemented changes and update any affected project documentation using the update-docs skill.
