codd-init

CoDD Init

Initialize CoDD in the current project, then move immediately into the first scan and validation cycle so the dependency graph starts from a clean baseline.

Usage

Run this skill when a repository does not have a codd/ directory yet and you need to bootstrap CoDD with the official codd CLI entry point.

Instructions

1. Preflight before running codd init:

   • Work from the project root where codd/ should be created.
   • If codd/ already exists, do not re-run init. Inspect the existing CoDD setup instead.
   • If the codd command is not available, install the package so the console script is on PATH before continuing.

2. Collect the required inputs:

   • Project name: default to the current directory name unless the user provides a better product name.
   • Primary language: choose one of python, typescript, java, or go.
   • Requirements file (optional): if the user already has a requirements document (any format — .txt, .md, .doc), use --requirements to import it. CoDD adds frontmatter automatically.

3. Choose the command:

   • With existing requirements file (recommended):

codd init --project-name "<project-name>" --language <language> --requirements <path-to-requirements> --dest .

• Without requirements (user will add them later):

codd init --project-name "<project-name>" --language <language> --dest .

1. Run the selected codd init command.

2. Confirm the generated skeleton:

   • codd/codd.yaml
   • codd/scan/
   • codd/reports/
   • codd/.gitignore
   • .codd_version

3. For an existing project, handle the bootstrap carefully:

   • Do not assume old design docs already have CoDD frontmatter. Inspect them before the first scan.
   • Prefer adding frontmatter to the documents you want CoDD to track before treating scan results as authoritative.
   • Legacy annotation files under codd/annotations/ are optional and backward-compatible. Create them only if the project still uses that workflow.