zeus-init

Zeus Init - Bootstrap Contract

Use this skill as the mandatory first step before any other /zeus:* workflow.

Non-negotiable rules

1. Ask one question per message and wait for the user's response.
2. Never create planning artifacts before config baseline is valid.
3. Always append an AI log after write operations.
4. If initialization already exists, require explicit user confirmation before overwrite.

Preconditions

• Workspace contains .zeus/ scaffold and schema files.
• You can write under .zeus/main/.
• Git repository is available (or can be initialized).

Brownfield mode

When --import-existing is provided:

• Read .zeus/{version}/codebase-map.json if present.
• Read .zeus/{version}/existing-modules.json if present.
• Pre-fill project.domain and project.tech_stack from discovered artifacts.
• Keep one-question loop to let user confirm or override inferred values.

Required context files

• .zeus/schemas/config.schema.json
• .zeus/main/config.json (if already present)
• .zeus/main/evolution.md (if already present)

Deterministic workflow

1) Initialization state check

Inspect whether .zeus/main/config.json exists and has a non-empty project.name.

• If initialized: explain current state and ask whether to re-initialize.
• If user declines: stop and suggest /zeus:status.
• If not initialized: continue.

2) Collect baseline inputs (single question loop)

Collect, in this exact order:

1. Project name
2. Primary domain (optional)
3. Technology stack
4. Version intent (single version or future v2/v3 tracks)

If --import-existing is active, show inferred values before each question as defaults.

3) North star metric proposal

Propose one recommended metric bundle with rationale and editable weights.

Output template:

Recommended metric strategy:

North star: {metric_name}
Weights:
- {metric_a}: {weight} ({reason})
- {metric_b}: {weight} ({reason})

Choose one:
A) Accept
B) Adjust weights
C) Fully customize