What problem does it solve? After a code change lands, durable project knowledge (AGENTS.md context files, feature scope checklists, and spec status lines) drifts out of sync with what the repository actually shows. This Skill closes that loop by surgically updating documentation to match the diff, without rewriting curated prose or sprawling beyond its mandate. ## Core Features & Use Cases - Surgical AGENTS.md maintenance: Edits existing root and nested AGENTS.md files line by line, creates nested docs only for areas net new in the change, and cleans up orphaned docs after deletions. - Scope and spec reconciliation: Ticks completed scope sub tasks based on repository evidence, advances feature statuses, and reconciles spec Status lines (Proposed, In Progress, Accepted) to match their linked features. - Tool discovery with consent: Detects newly added dependencies from manifest diffs and, only after explicit approval, searches for relevant Agent Skills and MCP servers to install. - Use Case: After merging a feature branch that adds a new payments module, run /sync to create a nested payments/AGENTS.md, tick the completed scope sub tasks, flip the spec status to Accepted, and flag any stale specs for /architect review. ## Quick Start Run the sync skill after merging my latest change to update AGENTS.md files, the feature scope, and spec statuses to match the repository.
