Install in 5 minutes.

Install the toolchain

Sulis delegates to a set of CLI tools — git, gh, python3, plus optional analysis and code-health scanners. Get them in place first, so every Sulis skill works from your very first session. One line installs them all:

curl -fsSL https://sulis.dev/install.sh | bash -s -- --all

Or if you'd rather read the script before running it:

curl -fsSL https://sulis.dev/install.sh -o install-sulis.sh
less install-sulis.sh                 # review
bash install-sulis.sh --check         # audit, no changes
bash install-sulis.sh --all           # install everything

Layered: core (required — git, gh, python3, pipx), analyse-codebase (default — ast-grep, lizard, scc, detect-secrets), code-health (optional — hadolint, trivy, gitleaks, semgrep, ruff, mypy and others). Missing tools degrade gracefully — the skills that need them report "not assessed" instead of failing. See What's installed for what each tool is for.

Add the marketplace

In Claude Code, run:

/plugin marketplace add sulis-ai/agents

This points Claude Code at the Sulis plugin marketplace on GitHub. It doesn't install anything yet — it just tells Claude Code where to find Sulis plugins.

Install the plugin

/plugin install sulis@sulis-ai-agents

This installs Sulis into your Claude Code setup. The plugin contains:

• The Sulis agent — your single point of contact, your VP of engineering. Talk to this one; it coordinates the rest.
• A team of specialist agents — backend engineer, requirements analyst, architect, executor, security reviewer, context cartographer.
• A library of skills Sulis runs on your behalf — speccing, designing, building, reviewing, and shipping.

The install runs locally. Nothing is uploaded.

Start your first session

From the root of your Git repo, run:

claude --agent sulis:sulis

Claude Code loads with Sulis as the active agent. You'll see a greeting and a prompt — ready for the next command.

Or run it autonomously. Sulis is designed to take a piece of work end-to-end — spec, design, build, review, ship — without pausing for permission at every step. To let it work that way, add the autonomous flag:

claude --dangerously-skip-permissions --agent sulis:sulis

With the flag, Sulis runs the full cycle hands-off. Every action is still recorded as a Git commit on a branch you review before merging, and every step is logged — but you're not interrupted along the way. Use it when you trust the session.

Set up the project

Sulis works on a per-project basis. Once the session is open, register this repo as a Sulis project:

/sulis:discover-project

Sulis looks around the repo, proposes a project name, and confirms it with you before minting the project record. Run this once per repo. Sulis re-uses the project record for every subsequent change.

Start your first change

Every piece of work in Sulis starts with the same command. Tell Sulis what you want to build, fix, or harden:

/sulis:change start "fix the login bug"

Sulis picks the kind of change (a primitive — fix, feat, harden, decompose, and so on), creates an isolated branch and worktree, and opens a fresh terminal already focused on the work. From there, the whole lifecycle — spec, design, build, review, ship — happens inside that change.

If you want the full picture before you start, read /sulis:change — the operating model. It's the most important command in Sulis; everything else happens inside a change.