init

Initialize Project with Digital Service Orchestra

Set up a new project to use Digital Service Orchestra by auto-detecting the stack and writing a workflow-config.yaml with sensible defaults.

Usage

/dso:init              # Initialize current directory
/dso:init [project-dir] # Initialize a specific directory

---

Steps

Step 1: Detect Stack

Run detect-stack.sh to identify the project type:

STACK=$(bash ".claude/scripts/dso detect-stack.sh" "${PROJECT_DIR:-.}")

The script inspects marker files and returns one of:

• python-poetry — pyproject.toml found
• rust-cargo — Cargo.toml found
• golang — go.mod found
• node-npm — package.json found
• convention-based — Makefile with ≥2 standard targets
• unknown — no recognized markers

Step 2: Map Stack to Default Commands

Use the detected stack to populate sensible command defaults:

Stack	test	lint	format	format_check
python-poetry	make test	make lint	make format	make format-check
node-npm	npm test	npm run lint	npm run format	—
rust-cargo	cargo test	cargo clippy	cargo fmt	cargo fmt --check
golang	go test ./...	golangci-lint run	gofmt -l .	—
convention-based	make test	make lint	make format	—

Additional defaults for python-poetry:

• validate: .claude/scripts/dso validate.sh --ci

Step 3: Check for Existing Config

Before proposing, check if workflow-config.yaml already exists using read-config.sh:

EXISTING_STACK=$(bash ".claude/scripts/dso read-config.sh" stack "${PROJECT_DIR:-.}/workflow-config.yaml")

If the file exists, warn the user and ask for confirmation before overwriting.

Step 4: Show Proposed Config

Present the proposed workflow-config.yaml to the user before writing:

# workflow-config.yaml — generated by /dso:init
version: 1
stack: <detected-stack>

commands:
  test: <default-test-command>
  lint: <default-lint-command>
  format: <default-format-command>
  # format_check: <default-format-check-command>  # if applicable
  # validate: <validate-command>                  # if applicable

Step 5: Write Config (with Overwrite Guard)

Write workflow-config.yaml to the project directory.

• If the file does not exist: write directly.
• If the file already exists: ask the user to confirm overwrite before proceeding.

  workflow-config.yaml already exists. Overwrite? (yes/no)
  

  If the user says no, abort and report the existing file path.

---

Escalation: Unknown Stack

If detect-stack.sh returns unknown, do not guess. Instead:

1. Report that no recognized stack markers were found.
2. Ask the user to specify the commands manually:

   No recognized stack found in <project-dir>.
   Please provide:
     - test command (e.g., 'make test'):
     - lint command (e.g., 'make lint'):
     - format command (e.g., 'make format', or leave blank):
   

3. Use the user-provided values to populate workflow-config.yaml.

---

Stack Default Reference

python-poetry

version: 1
stack: python-poetry
commands:
  test: make test
  lint: make lint
  format: make format
  format_check: make format-check
  validate: .claude/scripts/dso validate.sh --ci

node-npm

version: 1
stack: node-npm
commands:
  test: npm test
  lint: npm run lint
  format: npm run format

rust-cargo

version: 1
stack: rust-cargo
commands:
  test: cargo test
  lint: cargo clippy
  format: cargo fmt
  format_check: cargo fmt --check

golang

version: 1
stack: golang
commands:
  test: go test ./...
  lint: golangci-lint run
  format: gofmt -l .

convention-based

version: 1
stack: convention-based
commands:
  test: make test
  lint: make lint
  format: make format

---

Error Handling

Situation	Response
project-dir does not exist	Report error, abort
Stack is unknown	Escalate to user for manual input
workflow-config.yaml exists	Warn user, ask to confirm overwrite
User declines overwrite	Abort, show path to existing file