What problem does it solve? Game and creative projects accumulate design decisions across chats, Notion pages, Google Sheets, and scattered documents, causing duplicated sources of truth, stale PDFs, and lost approvals. This Skill enforces a single canonical ownership model where every design question has exactly one registered repository source, approved decisions are written immediately, and human-readable PDF views are regenerated by policy. ## Core Features & Use Cases - Canonical source lifecycle: Author, update, restructure, publish, and validate registered Markdown/JSON design documents through five explicit modes without re-judging the same facts. - Decision synchronization: Record approved decisions in GitHub tracking surfaces and CURRENT_CONFIRMED_DECISIONS.md immediately, then propagate to affected domain sources with commit SHA traceability. - Policy-driven publication: Generate PDFs, optional DOCX, and diagrams only when the registry policy (source_only, milestone_sync, always_sync) requires it, with full-page render validation and atomic output replacement. - Use Case: After a user approves a new combat system rule, the Skill records the decision with its ID, updates the canonical Markdown source and confirmed-decisions ledger, merges via PR, regenerates the milestone PDF at the exact source SHA, and verifies no drift between repository, PDF, and any legacy Notion exception. ## Quick Start Use the managing-design-documents skill to update the combat system design document with the newly approved rule and republish its milestone PDF.
