Set Up a New Venture
Invocation: As your first action, call
crane_skill_invoked(skill_name: "new-venture"). This is non-blocking — if the call fails, log the warning and continue. Usage data drives/skill-audit.
This command walks through setting up a new venture with Crane infrastructure.
Before running this command, the user must have completed:
Ask the user for:
dcdraftcrane)Confirm all values before proceeding.
Read the full setup checklist for reference:
cat docs/process/new-venture-setup-checklist.md
This is the canonical checklist. Follow it step by step.
The script automates most of the process:
./scripts/setup-new-venture.sh {venture-code} {github-org} {installation-id}
Dry run first to preview what will happen:
DRY_RUN=true ./scripts/setup-new-venture.sh {venture-code} {github-org} {installation-id}
The script handles:
config/ventures.json) - single source of truthAfter the script completes, walk through remaining manual steps from the checklist:
crane {venture-code} and /sos in the new repodocs/standards/golden-path.md PWA section and docs/process/new-venture-setup-checklist.md Phase 4.7 for step-by-step.Update CLAUDE.md in crane-console to reference the new venture in the Secrets Management section if not already there.
Run through Phase 5 of the checklist:
crane {venture-code} launches without errors/sos creates session and shows correct context/eos creates handoff successfullydocs/process/new-venture-setup-checklist.mdscripts/setup-new-venture.shconfig/ventures.json (single source of truth for ventures and INFISICAL_PATHS)workers/crane-context/src/constants.tsdocs/infra/secrets-management.md