// Reverse-propagate source code changes back to affected CoDD design documents. Use after code changes when the user needs to map changed source files to modules, identify impacted design docs, and optionally update those docs while preserving CoDD coherence.
Assemble generated CoDD sprint fragments into a complete, buildable project. Use after all `codd implement` sprints have produced `src/generated/sprint_N/` fragments and the design documents are ready to be integrated into final project files, entry points, source code, and configuration.
Generate CoDD design documents for a greenfield project one wave at a time. Use after `codd init` and prepared requirements when the user needs requirement-driven design docs, frontmatter validation, graph refresh, and human approval gates between waves.
Analyze the downstream impact of changed requirements, design docs, code, or tests in a CoDD project. Use when the user needs to decide which CoDD artifacts should be updated next, whether autonomous propagation is allowed, or whether a human approval gate is required.
Initialize CoDD in a project and establish the first scan and validation baseline. Use when a repository does not yet have a `codd/` directory, when importing initial requirements, or when bootstrapping greenfield or brownfield CoDD project structure.
Reconstruct CoDD design documents from extracted code facts for a brownfield project. Use after `codd extract` and wave planning when the user needs to infer requirements or restore system and detailed design from existing source code rather than greenfield requirements.
Refresh a CoDD project's dependency graph from document frontmatter and source code. Use after changes to requirements, design docs, implementation, or tests when the user needs current graph data, frontmatter coverage, node and edge counts, or warnings before validation or impact analysis.
| name | codd-propagate |
| description | Reverse-propagate source code changes back to affected CoDD design documents. Use after code changes when the user needs to map changed source files to modules, identify impacted design docs, and optionally update those docs while preserving CoDD coherence. |
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.
Do NOT use this for:
/codd-impact instead/codd-generate (greenfield) or /codd-restore (brownfield)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.
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
Before running propagate, verify:
codd/codd.yaml exists with source_dirs configured in scan.modules field in their frontmatter.--diff target).If modules fields are missing, run codd plan --init to regenerate wave_config with modules, then regenerate or restore design docs.
codd propagate --path .
This shows:
--update if updates are neededReview the analysis before deciding whether to update.
codd propagate --path . --update
This additionally:
After update, review every changed document before committing.
--update.Not every code change needs a design doc update. The AI prompt explicitly tells the model to leave the body unchanged for:
Use analysis-only mode (codd propagate without --update) to check which docs are affected, then decide manually whether an update is warranted.
| Flag | Description |
|---|---|
--path | Project root (default: current directory) |
--diff | Git diff target (default: HEAD) |
--update | Actually update affected docs via AI (default: analysis only) |
--ai-cmd | Override AI command for this run |
After modifying source code:
# 1. Check reverse impact (code → docs)
codd propagate --path .
# 2. If design docs need updating
codd propagate --path . --update
# 3. Rebuild dependency graph
codd scan --path .
# 4. Check forward impact (doc → doc) if design docs changed
codd impact --path .
# 5. Validate and commit
codd validate --path .
git add -A && git commit
No changed files detected
--diff target (e.g. --diff HEAD~3).No affected design docs found
source_dirs is configured in codd.yaml → scan.modules fields in their frontmatter.src/auth/service.py maps to module auth).--update. If the AI output is still bad, manually edit the doc.codd command, not python -m codd.cli.--update) to confirm affected docs before updating.codd impact in the same step — propagate handles code→doc, impact handles doc→doc.--update, always run codd scan to refresh the dependency graph.