ultracode-initlisted

# UltraCode Init ## Respect explicit Help precedence If the request explicitly invokes `$ultracode-help` or `ultracode-help`, stop before discovery or initialization. Read `../ultracode-help/SKILL.md` and answer `init` as a read-only Help topic. Initialize the current repository through inspection, a short interview, a reviewable proposal, and idempotent writes. Never clone another project's domain facts. ## Read the canonical protocol Read these sibling resources completely before proposing files: - `../ultracode/references/project-adapter.md` - `../ultracode/references/command-interface.md` - `../ultracode/references/control-and-status.md` - `../ultracode/references/swarm-protocol.md` - `../ultracode/references/reasoning-routing.md` - `../ultracode/references/project-config.schema.json` - `../ultracode/references/managed-manifest.schema.json` Follow active repository instructions. Invoking this skill authorizes a configuration proposal, not arbitrary code changes, Git operations, dependency changes, or overwriting existing AI guidance. ## Inspect before asking Work read-only first: 1. Find repository roots, active `AGENTS.md` files, manifests, source and test roots, CI, build files, existing docs, and Git status. 2. Inspect existing `.ultracode`, `.agents`, `.codex`, `.claude`, `CLAUDE.md`, and `CLAUDE.local.md` structures. 3. Detect real commands and label each `VERIFIED`, `INFERRED`, or `UNKNOWN`. Explain these as confirmed by evidence, found but not executed