codd-assemble

CoDD Assemble

Assemble generated sprint fragments into a complete, buildable project. This is the final step in the greenfield pipeline after codd implement.

Usage

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.

Prerequisites

1. codd implement has been run for all sprints.
2. Generated fragments exist in src/generated/sprint_N/ directories.
3. Design documents exist in docs/ with valid frontmatter.

Workflow

# 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 ""'

What It Does

1. Collects all design documents (architecture, component design, state management, etc.)
2. Collects all generated code fragments from src/generated/sprint_N/
3. Builds a prompt with both design context and code fragments
4. Invokes AI to produce a unified project:
   • Project configuration: package.json, tsconfig.json, next.config., tailwind.config., etc.
   • Entry points: app/layout.tsx, app/page.tsx, globals.css, etc.
   • Source code: components, utilities, types, hooks, reducers
5. Parses === FILE: path === blocks from AI output and writes files

Output

Files are written relative to the project root. The assembler produces both:

• Configuration files at the project root (package.json, tsconfig.json, etc.)
• Source files under the output directory (default: src/)

HITL Gate

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:

• Missing imports between assembled files
• Configuration mismatches (TypeScript strict mode, module resolution)
• Framework-specific entry point conventions