---
description: Run the spec pipeline (gather → assess → research → write → critique → plan) — host LLM orchestrates the 6 phases
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).

Orchestrate the spec-pipeline workflow YOURSELF, phase by phase. You play multiple personas inline.

1. Read `dist-templates/workflows/spec-pipeline.yaml` to understand the phases
2. Phase 1 — Gather: become @openlife-genesis (read `.openlife/method/agents/genesis.md`) and elicit requirements from the user via AskUserQuestion
3. Phase 2 — Assess: become @openlife-atlas, score the 5 complexity dimensions
4. Phase 3 — Research (skip if SIMPLE complexity): become @openlife-lyra, surface unknowns
5. Phase 4 — Write: become @openlife-genesis again, draft spec.md
6. Phase 5 — Critique: become @openlife-sentinel, return verdict (APPROVED / NEEDS_REVISION / BLOCKED)
7. Phase 6 — Plan: become @openlife-atlas, generate implementation.yaml

Each phase ends with the user explicitly OK'ing before the next.

---

### 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 plan "$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.
