sync

Run /sync as the last step after a change completes or merges. It diffs the change set against the base branch, updates existing root and nested MEMORY.md files with surgical line edits, and creates nested docs only for areas that are net new in the change.

The skill maps each spec's linked feature to its scope status and edits only the spec's Status line: planned becomes Proposed, in-progress becomes In Progress, and done becomes Accepted. Ambiguous or superseded specs are flagged for /architect instead of edited.

No. Creating or restructuring the root MEMORY.md is owned by /audit, and /sync only flags it as a context gap. /sync edits existing docs, creates nested docs for net-new areas, and never rewrites curated prose.

No. When dependency manifests change, it names the newly added tools and asks for explicit consent before searching. Nothing is searched, fetched, or installed until the engineer picks an option, and declines are recorded in MEMORY.md.

It reports NOTHING_TO_SYNC, which is a valid success outcome. If the change set contains only docs, tests, lock files, or generated output after filtering, it stops early without spawning any maintenance work.

The skill may only edit a spec's Status line, never its content. When a change contradicts a specific decision in a spec, or a later spec supersedes it, /sync flags the file and recommends running /architect to update or supersede it.