cdd-doc-update

Synchronize documentation for DONE decisions by updating referenced docs from gathered_context.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/yutaro0915/cdd-workflow --skill cdd-doc-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdd-doc-update
Source: https://github.com/yutaro0915/cdd-workflow/tree/main/src/templates/skills/cdd-doc-update
Command: npx skills add https://github.com/yutaro0915/cdd-workflow --skill cdd-doc-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize documentation for DONE decisions by aligning related docs with gathered_context.

Core Features & Use Cases

  • Find DONE decisions with docSyncStatus NOT_SYNCED and implementationStatus DONE across the project.
  • Read each cdd.md to extract gathered_context and the decision rationale, then update referenced documents accordingly.
  • Preserve existing content; only append or modify sections as guided; mark docSyncStatus SYNCED after successful updates.

Quick Start

Identify DONE decisions requiring documentation sync, read their cdd.md, and update the referenced documents based on gathered_context.

Frequently Asked Questions about cdd-doc-update

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

FAQPage Schema
How do I automate documentation sync for completed decisions?

Automating documentation sync for completed decisions involves identifying DONE implementation statuses and aligning referenced docs with gathered_context. This Skill scans cdd.md files where implementationStatus is DONE and updates linked documents based on extracted decision rationale.

What is the best way to update referenced documents based on gathered context?

Updating referenced documents based on gathered context requires extracting rationale from cdd.md and appending guided sections. This Skill reads gathered_context, modifies referenced docs while preserving existing content, and marks docSyncStatus as SYNCED after successful updates.

Can I preserve existing content while syncing decision management documentation?

Preserving existing content while syncing decision management documentation is supported by only appending or modifying sections as guided. This Skill ensures existing document content remains intact while adding new context from gathered_context during the synchronization process.

How does doc sync status tracking work for DONE decisions?

Doc sync status tracking for DONE decisions works by scanning for docSyncStatus NOT_SYNCED and updating it to SYNCED. This Skill locates cdd.md files where implementationStatus is DONE and docSyncStatus is NOT_SYNCED, then flips the status after applying gathered_context updates.

When do I need to synchronize documentation for completed decision implementations?

Synchronizing documentation for completed decision implementations is needed when implementationStatus reaches DONE but docSyncStatus remains NOT_SYNCED. This Skill targets that specific gap, ensuring referenced documents reflect the finalized gathered_context and decision rationale.

What happens if decision documentation sync fails or encounters limitations?

Decision documentation sync limitations arise when cdd.md files lack gathered_context or referenced documents are inaccessible. This Skill requires valid gathered_context to guide updates and cannot sync decisions missing the DONE implementationStatus or proper NOT_SYNCED docSyncStatus markers.