codd-propagate

CoDD Propagate

Reverse-propagate source code changes to design documents. When source code changes, codd propagate identifies which design docs are affected via the modules field and optionally updates them using AI.

When to Use

• After modifying source code and before committing
• When you want to check which design docs are affected by code changes
• When you want to auto-update design docs to reflect code changes
• As part of the modification flow (code changed → propagate → review → commit)

Do NOT use this for:

• Document-to-document propagation — use /codd-impact instead
• Initial design doc generation — use /codd-generate (greenfield) or /codd-restore (brownfield)

Propagation Direction

CoDD supports two propagation directions:

Direction	Command	Trigger	Mechanism
Forward (doc → doc)	codd impact	Design doc changed	CEG dependency graph (depends_on)
Reverse (code → doc)	codd propagate	Source code changed	modules field in frontmatter

/codd-propagate handles the reverse direction only.

How It Works

git diff HEAD              # 1. Detect changed source files
  ↓
source_dirs mapping        # 2. Map files to modules (e.g. src/auth/service.py → "auth")
  ↓
modules field lookup       # 3. Find design docs with matching modules
  ↓
Analysis report            # 4. Show which docs need attention
  ↓ (--update only)
AI update                  # 5. AI updates affected doc bodies

Prerequisite Checks

Before running propagate, verify:

1. codd/codd.yaml exists with source_dirs configured in scan.
2. Design docs have modules field in their frontmatter.
3. There are uncommitted source code changes (or specify --diff target).
4. Confirm you are in the intended project root.

If modules fields are missing, run codd plan --init to regenerate wave_config with modules, then regenerate or restore design docs.

Recommended Workflow

Analysis Only (Default)