cdd-integrator

Merge completed track knowledge into global specifications and archive tracks.

Updated Mar 12, 2019

Search Tags:#architecture #integration #specifications #glossary #archival #knowledge-management #track

Ready to run

npx skills add https://github.com/gustavofsantos/dot-files --skill cdd-integrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cdd-integrator
Source: https://github.com/gustavofsantos/dot-files/tree/main/.agents/skills/cdd-integrator
Command: npx skills add https://github.com/gustavofsantos/dot-files --skill cdd-integrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges completed track knowledge into global specifications and archives the track, reducing fragmentation and manual coordination.

Core Features & Use Cases

Consolidates track artifacts (specifications, decisions, glossary terms) into centralized global context files.
Archives completed tracks to .context/archive/ to keep workspaces clean and enable easy recovery.
Provides a ready state for new work by refreshing context after archival.

Quick Start

Run a retrospective on the completed track, then archive it with cdd archive <track-name>, and finally refresh the context with cdd recite <track-name>.

Frequently Asked Questions about cdd-integrator

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

FAQPage Schema

How do I consolidate track knowledge into global specifications?▼

You consolidate track knowledge by merging completed track artifacts, such as specifications, decisions, and glossary terms, into centralized global context files. This process reduces fragmentation and ensures centralized knowledge management across product teams.

What is the best way to archive completed work streams for knowledge management?▼

The best way to archive completed work streams is moving them to a dedicated .context/archive/ directory after consolidating their artifacts. This maintains a clean workspace and enables easy recovery of finished product team tracks.

How do I refresh context after archiving a completed track?▼

You refresh context after archival by running a recite command on the archived track. This provides a ready state for new work by updating the active context files once the finished track artifacts are successfully consolidated.

When do I need to merge track artifacts into centralized global context files?▼

You need to merge track artifacts into centralized global context files during track closure across product teams. This satisfies requirements for consistent artifact consolidation and clean archival of finished work streams.

Does track archival require manual coordination across product teams?▼

Track archival does not require manual coordination across product teams. The process automatically consolidates specifications, decisions, and glossary terms into global context files before archiving the completed track.

Why does context fragmentation happen after finishing a work stream?▼

Context fragmentation happens because completed track artifacts remain scattered across local files. Consolidating these artifacts into centralized global specifications and archiving the track resolves this fragmentation.