Repository navigation
Sync Vision Command #63
Description
Activity
🔗 Related PRs
#1 - [codex] refresh METHOD signposts and legend structure [merged]
#5 - Shape release workflow and user migration docs [merged]
#6 - Automated Witness Capture (Cycle 0020) [merged]
#18 - Land 0030-0033 repo-truth and MCP debt fixes [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Migrated from Method backlog
This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.
Source backlog:
docs/method/backlog/cool-ideas/SYNTH_sync-vision-command.mdOriginal lane:
cool-ideasOriginal legend:
SYNTHOriginal backlog card
Sync Vision Command
Add a
method sync visioncommand that runs the Executive SummaryProtocol and refreshes
docs/VISION.mdas a bounded, provenance-carryingsignpost. It should inventory the governing repo surfaces, generate the
summary from repo truth, and attach a witness reference or manifest so a
later human or agent can inspect how the summary was derived.
This idea already surfaced in spirit once
method sync shipautomatedother signpost maintenance. A dedicated vision sync would make summary
refresh cheaper, more reproducible, and more agent-friendly than
manually re-running a large read/summarize pass with ad hoc prompts.