init-project

name	init-project
description	Project init: configure AGENTS.md and agent mode.

Init Project

Use this helper after Gemini's built-in /init has already created or refreshed the project's GEMINI.md.

This helper owns only the Orchestrarium overlay file:

• .gemini/.agents-mode.yaml

It must not replace Gemini's official runtime config in:

• .gemini/settings.json

Continuity contract

• Use one primary in-progress task at a time.
• Side requests may temporarily interrupt that task, but they do not replace it unless the user explicitly reprioritizes, cancels, or parks it.
• After any side request, explicitly resume the primary task and state the next concrete step.
• After an accepted phase or completed batch, continue to the next clear step unless a real gate blocks progression.
• Before claiming completion, reconcile the current result against the original request and any still-open required follow-up inside the same task.
• If a required next action is already known and still inside the current task, keep the task open instead of stopping at a partial batch.

Preset expansion table

Presets are init-time shortcuts only. They expand into canonical agents-mode keys. The preset name is NOT persisted in the file.

Key	default (safe-init)	absolute-balance (everyday center)	external-aggressive (aggressive external use)	correctness-first (no-time-limit correctness)	power-mode (hardest-task maximum result)	max-speed (speed-first)
consultantMode	disabled	internal	external	external	external	disabled
delegationMode	auto	auto	force	force	force	auto
parallelMode	auto	auto	force	auto	force	force
mcpMode	auto	auto	auto	force	force	auto
preferExternalWorker	false	false	true	true	true	false
preferExternalReviewer	false	true	true	true	true	false
externalProvider	auto	auto	auto	auto	auto	auto
externalPriorityProfile	balanced	balanced	balanced

correctness-first and power-mode lane-specific opinion counts:

• advisory.repo-understanding: 2
• advisory.design-adr: 2
• review.pre-pr: 2
• review.security: 2
• review.performance-architecture: 2
• review.ui-visual-correctness: 2
• all other lanes: 1

Routing conventions (not persisted as keys):

• same-host fast-path: under external-aggressive and max-speed, when neutral isolation is not required, allow per-invocation explicit self-provider override. Keep the stored file canonical; this is a routing rule, not a persisted key.
• overflow means spill, not serialize: under external-aggressive, internal slot saturation pushes independent eligible lanes into $external-worker, $external-reviewer, or $external-brigade by default.
• power-mode means hardest-task maximum useful result: start from the quality-first provider-priority profile, then combine correctness-first validation density with external-aggressive fan-out, while keeping neutral workdirs and production-only auto routing so the extra power does not become a hidden project-state or example-provider shortcut.

Steps

1. Verify the official Gemini bootstrap first.

   • Read the project's GEMINI.md.
   • If GEMINI.md is missing, stop and tell the user to run Gemini's built-in /init first.
   • Treat /init as the canonical owner for creating or refreshing GEMINI.md.

2. Read current overlay state.

   • Read .gemini/.agents-mode.yaml first.
   • If it is missing, read legacy .gemini/.agents-mode as compatibility input only.
   • If both local files are missing, fall back through pack-local global ~/.gemini/.agents-mode.yaml, pack-local global legacy ~/.gemini/.agents-mode, then the shared cross-pack global ~/.agents-mode.yaml (alongside ~/.claude.json), before applying built-in defaults. Each key resolves to the highest layer that defines it; layers compose, they do not replace each other wholesale.
   • If either file exists, normalize it to the current canonical format before presenting or trusting any values.
   • If any file exists, normalize the effective file to the current canonical format before presenting or trusting any values.
   • Any read of .gemini/.agents-mode.yaml that drives a decision should normalize the file to the current canonical format before trusting the flags.
   • Any read of the effective Gemini overlay that drives a decision should normalize that file to the current canonical format before trusting the flags.
   • If neither local nor global overlay exists, start from the canonical defaults below.
   • Preserve unknown keys when updating an existing file.

3. Read the canonical operator reference when it is available.

   • If the current repository includes docs/agents-mode-reference.md, read it and use it as the authoritative value-by-value reference.
   • If that document is not present in the installed runtime, rely on this skill's canonical schema and rules below instead of inventing extra Gemini-only keys.

4. Select a preset (optional).

   • Ask the user if they want to start from a preset: default, absolute-balance, external-aggressive, correctness-first, power-mode, or .

Rules

• Do not create or rewrite .gemini/settings.json.
• Do not pretend .gemini/.agents-mode.yaml is a Gemini-native runtime setting.
• Do not invent extra keys beyond the canonical overlay schema.
• Any read that drives a decision should prefer local .gemini/.agents-mode.yaml, then local legacy .gemini/.agents-mode, then global ~/.gemini/.agents-mode.yaml, then global legacy ~/.gemini/.agents-mode; normalize whichever file supplied the effective config into the canonical .yaml path in the same scope and do not recreate any legacy file.
• Gemini is WEAK MODEL / NOT RECOMMENDED on this line. If the user asks for externalProvider: gemini, accept it only as an explicit self-provider override for a manual example or compatibility run; ordinary auto routing must still avoid same-provider self-bounce.
• If the user asks for externalProvider: qwen, treat it as the same kind of manual example or compatibility run and keep it out of shipped or repo-local production profiles.

Terms and Abbreviations

• agents-mode: Orchestrarium operator configuration overlay for delegation, external provider routing, MCP use, and parallelism.
• reserve: symbolic supplemental read-only candidate for advisory/review lanes only; it is separate from primary providers and not valid for worker or mutating routes.
• reserveResolver: scalar agents-mode key that binds symbolic reserve to a concrete read-only resolver such as claude-sonnet, claude-wrapper, or wrapper:<command>.
• Gemini: Google Gemini provider line; here it is explicit example-only and WEAK MODEL / NOT RECOMMENDED.
• MCP: Model Context Protocol; protocol for exposing tools and resources to agent runtimes.
• Qwen: Qwen provider line; here it is explicit example-only and WEAK MODEL / NOT RECOMMENDED.
• WEAK MODEL / NOT RECOMMENDED: repository classification for example-only providers excluded from production auto routing.