---
description: Bootstrap or resume work — reads .openlife/project.json mode and routes to greenfield or brownfield flow
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash(openlife:*)
  - Grep
  - Glob
  - Agent
  - AskUserQuestion
---

**Mode:** host-native (the host LLM running this conversation answers directly — no external API key required).

Detect the project mode and route to the right workflow.

1. Read `.openlife/project.json` if it exists. Use its `mode` field (`greenfield` / `brownfield` / `not-applicable`).
2. If missing, ask the user via AskUserQuestion: "Is this a brand new project (greenfield) or existing codebase (brownfield)?"
3. Based on the answer, decide and announce the recommended workflow:
   - greenfield + fullstack → run `/openlife:flow:greenfield-fullstack`
   - greenfield + service → run `/openlife:flow:greenfield-service`
   - greenfield + ui → run `/openlife:flow:greenfield-ui`
   - brownfield + first time → run `/openlife:flow:brownfield-blueprint`
   - brownfield + already discovered → ask sub-mode (fullstack/service/ui)
4. If mode was just set, persist via `openlife project-mode set <mode>`.

---

### Want the external model chain instead?

If you specifically need the configured `models.json` chain (for cost-tracking, batch, or non-host contexts), run the command in a terminal:

```bash
openlife start "$ARGUMENTS"
```

That path uses the Brain dispatcher and requires the appropriate API key in `.env`. The slash command (this one) intentionally bypasses external APIs to keep host-CLI usage zero-config.
