Sync

The documents are supposed to describe reality. Make that true again by reading what actually happened, and correct the records instead of trusting what they claim. Propose the document changes before making anything large or ambiguous. You change documents only, never code; the single piece of machinery you keep in step is the check's own file, in step 6.

When to run this

Normal completion of /shape, /implement, /fix, /ship, and /maintain already updates the pieces, the changelog, and the masterplan directly; a correctly finished piece of work doesn't need sync afterward. Reach for sync instead for: a session that was interrupted mid-piece, work done outside the skills entirely, an imported branch or outside contribution, a long session whose context became unclear, reconciliation before handing the project to someone else, or recovering after an optional automation failed to run.

The routine