What problem does it solve? Code changes frequently leave project documentation stale: new EF migrations ship without schema doc updates, new services never appear in architecture docs, and completed epics go unrecorded. This Skill defines a standard that maps each code change type to the exact documents that must be updated, with freshness thresholds and audit tracking. ## Core Features & Use Cases - Code-to-Doc Impact Mapping: A priority-ranked table (P0/P1/P2) linking changes like EF migrations, SignalR hubs, middleware, and RBAC rules to specific docs such as database-schema.md and architecture/platform-services.md. - Freshness Enforcement: A 2-week (14-day) staleness threshold, last-updated source recording format, and last_synced_epic tracking scanned during Epic Closing Audits (TD-28). - Doc Index Infrastructure: Integrates with Context Memory DB tables (doc_index, document_chunks, document_embeddings) and scheduled scripts like scan-doc-index.js for automatic re-indexing. - Use Case: After adding a new EF Core migration, consult the mapping table to confirm database-schema.md is a P0 update, apply the change, and record the last-updated tag with version, date, and source story. ## Quick Start Ask the assistant to check which documents need updating after your latest code changes using the phycool-doc-sync mapping table.
