skills.rest
sunLeee
sunLeeeCOMMUNITY
Explore all skills by this author →
GitHub

sync-docs

Synchronize scenario-affected documents across PRDs, architecture, components, tasks, ADRs, and tests.

Updated Mar 19, 2026
Search Tags:#documentation#adr#traceability#scenario#doc-sync#documentation-updates
One-click install
npx skills add https://github.com/sunLeee/optimization --skill sync-docs-sunleee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-docs
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/utility/sync-docs
Command: npx skills add https://github.com/sunLeee/optimization --skill sync-docs-sunleee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automatically updates all related documentation when new scenarios or edge cases are added, ensuring traceability and consistency across upstream and downstream docs.

Core Features & Use Cases

  • Automated doc synchronization: Propagates scenario changes to linked documents to keep documentation aligned.
  • Traceability-driven updates: Identifies upstream and downstream documents affected by changes and applies updates consistently.
  • Context-aware execution: Responds to user requests or scenario edits to trigger synchronized documentation updates with auditability.

Quick Start

Invoke the sync-docs command with the target scenario file path to update all related documents.

Frequently Asked Questions about sync-docs

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

FAQPage Schema
How do I automatically update documentation when a scenario changes?▼

To update documentation when a scenario changes, you can propagate the edits to linked upstream and downstream documents, maintaining consistency and generating an auditable change summary.

What is traceability-driven documentation synchronization?▼

Traceability-driven documentation synchronization is the process of identifying and updating all affected PRDs, architectures, components, tasks, ADRs, and tests when scenarios are added, changed, or deprecated.

How do I keep PRDs and ADRs in sync with new edge cases?▼

You can keep PRDs and ADRs in sync with new edge cases by triggering context-aware updates that map scenario edits to affected documents and apply changes consistently across the project.

Can I generate a traceability mapping for upstream and downstream documents?▼

Yes, you can generate a traceability mapping for upstream and downstream documents, which surfaces the connections for review and enforces consistency across the entire workflow.

What is the best way to audit documentation updates after deprecating a scenario?▼

The best way to audit documentation updates after deprecating a scenario is to generate an auditable change summary that tracks all propagated updates across components, tasks, and tests.

Related Skills

Explore More Content & Communication Skills→
thieungthieung
1

/wiki:setup

Create and validate knowledge base vault directories and CLAUDE.md schema.

Community
Intermediate
carlosamesarcarlosamesar
1

sdd-archive

Merge delta specifications into main specs and archive completed changes.

Community
Intermediate
nesihaver-ILnesihaver-IL

update-docs

Update README, API, architecture docs, and changelogs after code changes.

Community
Intermediate
tim099tim099
4

ucl-translate-docs

Translate Markdown files with glossary checks and link preservation.

Community
Advanced