new-project

Scaffold a new coding-os project non-interactively — the official agent recipe (TASK-359).

Steps:

1. Discover what's available (read-only):
   • cos list-stacks --format json → stacks (grouped by language) + presets.
   • cos skills-list --stack <id> --format json → required/recommended/optional skills for a stack.
2. Preview the composition BEFORE writing anything:
   • cos init --preset <id> --dry-config (or --template a --template b --dry-config)
   • Read the swimlane union and the reported merge conflicts (later stack wins). Nothing is written.
3. Create in one shot (every Composer option has a flag — full parity, incl. multi-agent + module toggles):

cos init \
  --agent claude \                   # one+ adapters, comma-separated: --agent claude,codex
  --preset nextjs-fastapi \          # OR: --template go-fiber --template fastapi
  --name my-app -d /path/to/parent \ # omit --name only in interactive shells
  --skills redis,docker \            # extra core skills (validated; see cos skills-list)
  --profile standard \               # module surface: lite | core | standard (default) | full
  --disable-module memory \          # optional, repeatable: turn a subsystem off at create
  --summary "One to two paragraphs describing the product, its users, and what matters most." \
  --yes --no-index

1. Verify: exit code 0; --format json emits the summary object (path, slug, agents, templates, …). The project self-registers in the hub; --summary seeds docs/_meta/project-description.md (the description→PRD intake) and leaves _TODO: markers in the seeded PRD, so the panel still offers the guided interview.

Rules:

• Non-TTY without --yes fails fast naming the missing flags — never rely on prompts in automation.
• --preset and --template are mutually exclusive; unknown skills/stacks/presets exit 2 listing what exists.
• --agent takes one or more adapters (claude, codex), comma-separated — a project may host several.
• --profile <name> picks the module surface (cos init --help lists the live set from subsystems.yaml): lite = kernel only (discipline + safety, near-zero MCP tools — the MCP-averse adopter), core, standard (default: cognition + cicd off), full = everything. Omitting it applies the registry default, so a project can end up leaner than you expected — pass it explicitly when the surface matters.
• --disable-module <id> (repeatable) turns one subsystem off; ids come from subsystems.yaml (docs, tasks, graph, memory, cognition, observability, hub-extras, cicd). kernel can't be disabled and a module's dependents go with it (unknown/kernel exit 2).
• Profile and --disable-module are UNIONED — a profile can only ever remove more. --enable-module <id> (repeatable) is the escape: it force-enables a module after the union, pulls its depends_on chain in with it, and errors when the same id is also explicitly disabled; that is exactly what the Hub Composer sends for chips left on. cos module list shows the result.
• Don't pass --name you can't validate: ^[a-z0-9][a-z0-9._-]{0,63}$.