---
name: documentation-sync
description: "Synchronizes shared documentation with an implemented change and removes contradictory current-state guidance. Use when architecture, routes, content, brand, standards, ownership, or verification changed."
---

# Synchronize the living documentation

Apply this skill during **Operate** work. It supports Any stack.

Make the shared memory describe what now exists, why it changed, and how to verify it.

## Instructions

Synchronize documentation after inspecting the implemented change. Identify which shared source-of-truth documents are affected by architecture, routes, data ownership, branding, content, design standards, compatibility, or quality requirements. Update those documents to describe the current implementation, including exact commands, paths, owners, identifiers, constraints, and verification steps. Remove contradictions and superseded current-state guidance; preserve history only where it explains a compatibility decision. Do not create a new planning file when an existing shared document owns the topic. Finish by checking every documented path and command against the repository.

## Detect the problem

- Documentation still describes the proposal after the implementation changed
- A new readme created because the existing source of truth was not found
- Commands and file paths copied without checking that they exist

## Hold the gate

Do not declare this phase complete until every item passes:

- [ ] The code change is mapped to the exact architecture, content, brand, route, or QA source of truth it affects
- [ ] Documentation describes implemented current state rather than the original plan
- [ ] Commands, paths, identifiers, ownership, and compatibility constraints match the repository
- [ ] Superseded guidance is removed or explicitly marked historical without creating a competing document
- [ ] A fresh contributor can locate, change, and verify the affected system from the updated documentation

## Verify the result

Give the updated entry point to a fresh contributor; they must locate the implementation, name its constraints, and choose the correct verification command without help.