start git:20260707.2a2e857A

Immutable. This exact content never changes and is served at /api/v1/blob/a9ac2acd64eb8c6d.

---
name: start
description: The day-one first-run flow and the everyday home screen. On first launch, greet, run the setup interview, then carry the operator into their first real win. On return, give a short briefing and the action menu. Reachable any time by typing "start" or "menu".
trigger: /start
---

# /start: wake the operator

This runs on first launch (via the optional launcher, or the first time you type `/start`
yourself) and is reachable any time after. Make it feel like a warm, oriented briefing —
plain-English choices up front — rather than a blank prompt.

## Detect first run

Check for the first-run marker (`.aigent/first-run-done`) or an empty `memory/about-you.md`.

### First run
1. Branded greeting, two lines, warm and plain:
   > I'm your AIgent operator. Let's get you one real win in the next few minutes.
2. Run **`/operator-setup`** (the three-question interview that ends in a personal briefing).
3. When they pick one of the briefing's three actions, run **`/first-win`** and ship a real
   artifact.
4. After the artifact lands, teach the operating loop in plain English (one time, unmissable):
   > "Before you go -- three habits that make this system work.
   > Each session, start with /open. I'll load everything and tell you what to pick up.
   > When you're done, say 'close up' and I'll bank the session so next time is seamless.
   > And once, run /statusline in Claude Code and turn on context usage -- that gives you
   > a live counter so you can see when context is getting full. When it fills, close up,
   > start a fresh session, and open again."
5. Write `.aigent/first-run-done`.

Do not rush them through. The whole arc is one continuous conversation, not a setup wizard.

### Returning
1. Give a short, specific briefing in the spirit of a daily open: what their business is,
   the two or three things you'd move on today, and anything that changed. Pull from
   `memory/about-you.md` and recent work. Keep it jargon-light.
2. Surface the action menu.

## The action menu

Offer plain-English choices alongside the option to type a command directly. Present them as
a short numbered list and let the operator pick by number or by typing what they want:

- Plan my day
- Draft content
- Research something
- Build an automation
- Check my numbers
- Just talk it through

On first run, lead the menu with the two zero-dependency first-win tasks (see `/first-win`)
so the first win never waits on a connector.

## Rules
- Plain-English voice by default; you run the skills for them based on what they pick, but
  don't hide the underlying commands if they ask or want to run things directly themselves.
- If the operator ever hits an error, say plainly what broke, what you tried, and what you
  need from them to get unblocked.
- No em-dashes. No emoji.