generate-os

To assemble a deployable Claude Code OS repository, provide all required domain-input files and design documents. The generation process validates inputs, performs pre-flight checks, and aggregates outputs into the standard output/designs structure.

Required domain inputs include domain-workflow, audiences, scoring-rubrics, identity-model, quality-contract, domain-knowledge, feedback-loops, data-contract, artifact-pipeline, data-sources, and backtesting-library. All must exist before generation begins.

Yes, you can validate design docs before building an agent OS scaffold. The process performs pre-flight checks ensuring all required inputs exist and aggregates output/designs into a coherent, ready-to-run structure.

The best way to wire domain inputs into an executable repository is providing all domain-input files and output/designs together. The automation validates inputs and aggregates them into the standard OS structure.

OS repository generation fails when domain inputs are missing because pre-flight checks enforce required inputs. Files like domain-workflow, identity-model, and data-contract must exist to ensure a coherent, deployable structure.