What problem does it solve?
Project doctrine scattered across plans, docs, skills, and reviews drifts out of sync with the root VISION.md file, causing agents and maintainers to repeat past mistakes. This Skill incrementally classifies changed inputs and patches VISION.md with reusable project taste.
Core Features & Use Cases
- Incremental Diff Collection: A helper script collects changed durable inputs since the last synced commit, including working-tree overlays, and extracts candidate doctrine lines by category.
- Classification Ledger: Every candidate is classified as captured, reaffirmed, rejected, run-specific, owner-routed, or deferred-with-question, with baseline advancement only after full accounting.
- Owner Routing: Non-vision misses are routed to the owning skill, spec, research doc, or migration guide instead of polluting VISION.md.
- Use Case: After a week of merged plans and rule changes, run the sync command to patch VISION.md with new reusable doctrine and record a decision ledger in the run artifacts.
Quick Start
Ask the agent to run sync-vision to analyze changed inputs since the last synced commit and update the root VISION.md with any new reusable project doctrine.