Sync

Synchronize design-impacting changes from trace.md into arch.md.

1|Updated Jan 30, 2026

Search Tags:#documentation #sync #traceability #drift #design-sync #arch.md

Ready to run

npx skills add https://github.com/samdae/archflow --skill sync-samdae

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Sync
Source: https://github.com/samdae/archflow/tree/main/skills/sync
Command: npx skills add https://github.com/samdae/archflow --skill sync-samdae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize design-impacting changes from changelogs and enhancement results into arch.md to ensure traceability and reduce drift between requirements and implementation.

Core Features & Use Cases

Sync Debug Changes: Propagate design-impacting items from trace.md to arch.md.
Sync Enhancements: Integrate enhancement results into arch.md.
Drift Checking & Spec Updates: Detect requirement drift and optionally update spec.md to reflect reality.

Quick Start

Ensure docs/{serviceName}/trace.md and docs/{serviceName}/arch.md are prepared, then run the Sync workflow to merge changes into arch.md and mark items as synced in trace.md.

Frequently Asked Questions about Sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep arch.md in sync with design changes from my changelogs?▼

To keep arch.md in sync with design changes, the workflow reads trace.md and spec.md, merges design-impacting items into arch.md, and marks synced items in trace.md.

What is requirement drift and how do I detect it between spec.md and implementation?▼

Requirement drift occurs when implementation diverges from specifications; you can detect it by running a drift check that compares design changes against spec.md and optionally updates the spec to reflect reality.

How do I propagate debug fixes and enhancement results into architecture documentation?▼

You propagate debug fixes and enhancement results by reading design-impacting items from trace.md, merging those changes into arch.md, and optionally performing a Git backup before modifying the files.

Do I need to prepare trace.md and arch.md before running a design-sync workflow?▼

Yes, preparing docs/{serviceName}/trace.md and docs/{serviceName}/arch.md is required, as the workflow reads these files to merge changes and update traceability.

Can I update spec.md automatically when synchronizing architecture documentation?▼

Yes, you can update spec.md automatically; the synchronization workflow optionally detects requirement drift and updates spec.md to reflect the actual implementation state.