> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mutagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Your first loop

> From a fresh install to a spec, a build, and a first verdict — the whole ADLC loop in a few minutes.

Once Helix is installed and booted, you drive it in plain English. This page walks the shortest
path from nothing to a first verdict.

<Info>
  Not installed yet? Set up the [Plugin](/helix/install/plugin) or the
  [Standalone](/helix/install/standalone) binary first.
</Info>

## Start something new

Begin at Spec. Describe the agent you want — in this walkthrough, a support-triage agent:

```
I want a support-triage agent for inbound email
```

Helix runs a guided interview and emits `agentspec.yaml`, the definition of the agent. Then build it:

```
build it
```

Helix implements the spec into your framework or harness and stops at a working agent.

## Improve one you already have

If you already have an agent and some traces, go straight to Evaluate:

```
evaluate support-triage against my traces
```

Helix derives success criteria from the runs, scores each, and returns a verdict. Where it flags
failures, ask why:

```
why is support-triage mislabeling refund requests?
```

Diagnose returns ranked remedies. Nothing is applied until you approve; when you accept one, Helix
applies it and re-runs the loop so you can confirm it helped.

## You're done when

* The Helix dashboard renders, and
* `*spec` (or just asking for a spec) starts the interview.

A full `*evaluate` needs a subject and its traces — that's the loop proper, above.

<Tip>
  Prefer commands to prose? Every stage has a shortcut: `*spec`, `*build`, `*evaluate`, `*diagnose`,
  `*optimize`. They're alternatives to natural language, not requirements. See
  [Commands](/helix/reference/commands).
</Tip>