// 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.
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.
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-assemble |
| description | 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. |
Assemble generated sprint fragments into a complete, buildable project. This is the final step in the greenfield pipeline after codd implement.
Use this skill after all sprints have been generated via codd implement. The assembler reads design documents and generated code fragments, then invokes AI to produce a unified project with all configuration files, entry points, and source code.
codd implement has been run for all sprints.src/generated/sprint_N/ directories.docs/ with valid frontmatter.# Basic usage — assembles into src/
codd assemble --path .
# Custom output directory
codd assemble --path . --output-dir app
# Override AI command (e.g., use a different model)
codd assemble --path . --ai-cmd 'claude --print --model claude-opus-4-6 --tools ""'
src/generated/sprint_N/=== FILE: path === blocks from AI output and writes filesFiles are written relative to the project root. The assembler produces both:
src/)After assembly, verify the project builds:
# For Node.js/TypeScript projects
npm install
npm run build
# For Python projects
python -m pytest
If the build fails, check:
#!/bin/bash
set -e
codd init --requirements spec.md
codd plan --init
waves=$(codd plan --waves)
for wave in $(seq 1 $waves); do
codd generate --wave $wave
done
codd validate
sprints=$(codd plan --sprints)
for sprint in $(seq 1 $sprints); do
codd implement --sprint $sprint
done
# Final step: assemble fragments into a working project
codd assemble
No generated fragments found in src/generated/
codd implement first. Fragments are created per sprint.--ai-cmd pointing to a more capable model (e.g., Opus) for better integration.