@openlife/cli 1.8.3 → 1.9.3

package/dist-templates/claude-code/commands/openlife/audit.md

@@ -0,0 +1,14 @@
+---
+description: Run brownfield-discovery — 10-phase audit of an existing codebase
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run brownfield-discovery "$ARGUMENTS"`. The 10-phase audit produces architecture, schema, frontend specs, technical-debt assessment, and a backlog of remediation stories.

package/dist-templates/claude-code/commands/openlife/doctor.md

@@ -1,19 +1,16 @@
 ---
 description: Run OpenLife health checks (API keys, model chain, runtime catalogs, daemon state)
-allowed-tools: Bash(openlife:*)
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
 ---
 
-Run `openlife system doctor` and walk the user through the results.
+Run `openlife system doctor` and walk the user through results.
 
-For each failed check:
-1. Quote the failure line
-2. Explain in 1 sentence what the check verifies
-3. Suggest the concrete fix (usually setting an env var or running a follow-up command)
-
-Common failures and fixes:
-- **Missing `GEMINI_API_KEY` / `OPENAI_API_KEY` / `ANTHROPIC_API_KEY`** → add to `.env` at project root
-- **Missing `TELEGRAM_BOT_TOKEN`** → only required if profile is `autonomous`
-- **Catalog empty** → run `openlife system setup` (likely incomplete install)
-- **Ollama not reachable** → optional unless `OPENLIFE_ENABLE_OLLAMA=true`
-
-If everything passes, say so concisely — don't pad.
+For each failed check: quote the line, explain in 1 sentence what it verifies, suggest the concrete fix.

package/dist-templates/claude-code/commands/openlife/dream.md

@@ -1,20 +1,14 @@
 ---
 description: Run the OpenLife Dream Organizer — surfaces ideas, pending stories, and prioritization from accumulated context
-allowed-tools: Bash(openlife:*)
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
 ---
 
-Run `openlife dream` (the Dream Organizer) and present the output as a ranked list of next actions for the user.
-
-The Dream Organizer reads:
-- Conversation memory (last sessions)
-- Pending stories in `docs/stories/`
-- Open governance consents in `.openlife/governance-consents.json`
-- Mission state in `.openlife/`
-
-Format the output as:
-
-1. **Top 3 priorities** — the highest-signal items with one-line justification
-2. **Deferred** — items the Dream Organizer parked
-3. **Open questions** — anything the user needs to decide before work can proceed
-
-Don't make up items the command didn't return.
+Run `openlife dream "$ARGUMENTS"` to surface unprioritized ideas and stories from memory. Present the output grouped by theme.

package/dist-templates/claude-code/commands/openlife/explore.md

@@ -0,0 +1,14 @@
+---
+description: Exploratory ideation with Lyra — divergent brainstorming, then convergent narrative
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Activate `@openlife-lyra` (reads `.openlife/method/agents/lyra.md`) and run `*brainstorm "$ARGUMENTS"`. Surface options + tradeoffs. Do NOT commit to a plan in this command — that's `/openlife:plan`.

package/dist-templates/claude-code/commands/openlife/flow/brownfield-discovery.md

@@ -0,0 +1,20 @@
+---
+description: Brownfield Discovery: 10-phase audit of an existing codebase
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run brownfield-discovery $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/brownfield-discovery.yaml` (or `.openlife/method/workflows/brownfield-discovery.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/brownfield-fullstack.md

@@ -0,0 +1,20 @@
+---
+description: Brownfield Full-Stack: enhance an existing full-stack app
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run brownfield-fullstack $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/brownfield-fullstack.yaml` (or `.openlife/method/workflows/brownfield-fullstack.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/brownfield-service.md

@@ -0,0 +1,20 @@
+---
+description: Brownfield Service: modify an existing service / API
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run brownfield-service $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/brownfield-service.yaml` (or `.openlife/method/workflows/brownfield-service.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/brownfield-ui.md

@@ -0,0 +1,20 @@
+---
+description: Brownfield UI: refactor or enhance an existing UI
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run brownfield-ui $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/brownfield-ui.yaml` (or `.openlife/method/workflows/brownfield-ui.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/epic.md

@@ -0,0 +1,20 @@
+---
+description: Epic Orchestration: coordinate multiple dependent stories within an epic
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run epic-orchestration $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/epic-orchestration.yaml` (or `.openlife/method/workflows/epic-orchestration.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/greenfield-fullstack.md

@@ -0,0 +1,20 @@
+---
+description: Greenfield Full-Stack: end-to-end new app from concept to shippable stories
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run greenfield-fullstack $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/greenfield-fullstack.yaml` (or `.openlife/method/workflows/greenfield-fullstack.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/greenfield-service.md

@@ -0,0 +1,20 @@
+---
+description: Greenfield Service: backend-only / API-only / CLI / worker / MCP server
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run greenfield-service $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/greenfield-service.yaml` (or `.openlife/method/workflows/greenfield-service.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/greenfield-ui.md

@@ -0,0 +1,20 @@
+---
+description: Greenfield UI: frontend-only / SPA / landing / admin panel / docs site
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run greenfield-ui $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/greenfield-ui.yaml` (or `.openlife/method/workflows/greenfield-ui.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/qa-loop.md

@@ -0,0 +1,20 @@
+---
+description: QA Loop: iterative review-fix cycle (max 5 iterations) between Sentinel and Builder
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run qa-loop $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/qa-loop.yaml` (or `.openlife/method/workflows/qa-loop.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/release.md

@@ -0,0 +1,20 @@
+---
+description: Continuous Deployment: release pipeline driven by Vortex (PR → merge → tag → publish)
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run continuous-deployment $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/continuous-deployment.yaml` (or `.openlife/method/workflows/continuous-deployment.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/spec-pipeline.md

@@ -0,0 +1,20 @@
+---
+description: Spec Pipeline: 6-phase gather → assess → research → write → critique → plan
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run spec-pipeline $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/spec-pipeline.yaml` (or `.openlife/method/workflows/spec-pipeline.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/flow/story-cycle.md

@@ -0,0 +1,20 @@
+---
+description: Story Development Cycle: 4-phase Create → Validate → Implement → QA
+argument-hint: "[--dry-run] [--vars key=value]"
+allowed-tools:
+  - Read
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run story-development-cycle $ARGUMENTS` and walk the user through the workflow as it executes.
+
+- The workflow YAML is at `dist-templates/workflows/story-development-cycle.yaml` (or `.openlife/method/workflows/story-development-cycle.yaml` if locally overridden).
+- Each phase invokes one or more OpenLife method agents.
+- On any failure: surface the failing step + which agent is responsible, then offer to escalate to `@openlife-maestro`.
+- `--dry-run` prints the phase plan without executing.
+
+Refer the user to the persona of the active phase when they ask "who is doing this?".

package/dist-templates/claude-code/commands/openlife/health.md

@@ -0,0 +1,14 @@
+---
+description: Extended health check — combines `doctor` with runtime diagnostics from Maestro
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife system doctor` first, then activate `@openlife-maestro` and run `*health` to check cross-agent integrity (catalog completeness, missing handoff artifacts, draft components pending promotion).

package/dist-templates/claude-code/commands/openlife/plan.md

@@ -0,0 +1,14 @@
+---
+description: Run the spec pipeline — gather requirements, assess complexity, write executable spec
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run spec-pipeline "$ARGUMENTS"`. The 6-phase pipeline: gather → assess → research → write → critique → plan. Walk the user through each phase's output.

package/dist-templates/claude-code/commands/openlife/review.md

@@ -0,0 +1,14 @@
+---
+description: Run the QA gate on a story (Sentinel) — 7-check verdict: PASS / CONCERNS / FAIL / WAIVED
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Activate `@openlife-sentinel` (reads `.openlife/method/agents/sentinel.md`) and run `*qa-gate "$ARGUMENTS"`. Pass the story id or the file path as the argument. Report the verdict + structured findings.

package/dist-templates/claude-code/commands/openlife/ship.md

@@ -0,0 +1,14 @@
+---
+description: Run the continuous-deployment workflow — release pipeline driven by Vortex
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Run `openlife flow run continuous-deployment "$ARGUMENTS"`. Vortex drives: pre-release QA, PR open, CI wait, merge, version bump, tag, publish. Maestro logs the release event at the end.

package/dist-templates/claude-code/commands/openlife/start.md

@@ -0,0 +1,25 @@
+---
+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
+---
+
+Detect the project mode:
+
+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, recommend a workflow:
+   - greenfield + fullstack → `openlife flow run greenfield-fullstack`
+   - greenfield + service → `openlife flow run greenfield-service`
+   - greenfield + ui → `openlife flow run greenfield-ui`
+   - brownfield + first time → `openlife flow run brownfield-discovery`
+   - brownfield + already discovered → ask sub-mode (fullstack/service/ui)
+4. If mode was just set, persist via `openlife project-mode set <mode>`.

package/dist-templates/claude-code/commands/openlife/status.md

@@ -1,14 +1,14 @@
 ---
 description: Show OpenLife system status — installed profile, host, catalog counts, daemon state
-allowed-tools: Bash(openlife:*)
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
 ---
 
-Run `openlife system status` and summarize the output for the user. Highlight:
-
-- **Profile** in use (framework vs autonomous)
-- **Host** target (claude-code / gemini-cli / codex)
-- **Catalog counts** (agents, skills, squads, mcps)
-- **Daemon state** if profile is autonomous
-- Any **doctor warnings** that need attention
-
-If the command fails, surface the exit code and stderr — don't hide the failure.
+Run `openlife status --json` and present a tight summary of: active profile, host CLIs installed, catalog counts (agents/squads/skills), daemon heartbeat freshness, telegram allowed user.

package/dist-templates/claude-code/commands/openlife/story.md

@@ -0,0 +1,18 @@
+---
+description: Create the next story from an epic (Conductor) or validate a draft (Steward)
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash(openlife:*)
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+
+Determine intent from $ARGUMENTS:
+
+- If the user wants to CREATE a story → activate `@openlife-conductor` (reads `.openlife/method/agents/conductor.md`) and run `*create-next-story`.
+- If the user wants to VALIDATE a draft → activate `@openlife-steward` and run `*validate-story`.
+- If unclear, ask via AskUserQuestion which action to take.

package/dist-templates/codex/agents/openlife-atlas.md

@@ -1,52 +1,20 @@
 ---
 name: openlife-atlas
-description: Codebase mapping and architectural analysis specialist. Use for dependency tracing, identifying which files/classes own a behavior, mapping subsystems, surfacing architectural drift, or producing the architecture section of a planning doc. Not for writing new code — that's the default flow. Not for prose writeups — that's LYRA.
-tools: Read, Grep, Glob, Bash
-model: sonnet
+description: System Architect in the OpenLife method — codebase mapping, ADRs, technology selection, impact analysis, complexity assessment
+tools: [Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion]
+model: claude-opus-4-7
 ---
 
-You are **ATLAS**, the codebase mapping specialist for OpenLife.
+You are **Atlas**, the System Architect in the OpenLife method.
 
-## What you own
+**Persona definition:** Read `.openlife/method/agents/atlas.md` in full before responding. It defines what you own (system architecture, tech selection, high-level data architecture, integration patterns, complexity assessment), what you delegate (DDL to Mesh, UI architecture to Prism, app code to Builder), and the 5-dimension complexity scoring (Scope, Integration, Infrastructure, Knowledge, Risk).
 
-- **Subsystem mapping**: Given a feature, identify every file/class involved
-- **Dependency tracing**: Where is X imported? What does Y depend on?
-- **Drift detection**: Compare current code structure to documented architecture (`.planning/codebase/ARCHITECTURE.md`, CLAUDE.md)
-- **Impact analysis**: If we change file A, what else breaks?
+**Activation:**
+1. Read the persona file
+2. Display: `🏛️ Atlas analyzing. Codebase mapped: <yes/no>. ADRs on file: <count>.`
+3. Show top 5 commands
+4. HALT and await `*command`
 
-## What you don't own
+**Slash command alias:** `/openlife:agents:atlas`
 
-- Writing application code → default Claude Code flow
-- Prose synthesis or PRDs → LYRA
-- Creating new agents/skills → FORGE
-- Project scaffolding → GENESIS
-
-## OpenLife architecture map (memorize)
-
-- **Entry**: `bin/openlife.js` → `dist/index.js` ← compiled from `src/index.ts` (lazy imports!)
-- **Orchestrator (80+ classes)**: `src/orchestrator/` — Brain, Gateway, IntentClassifier, GovernanceLayer, ...
-- **CLI/install**: `src/cli/` — SystemInstaller, InstallFlow (host-aware), AutonomousInstaller
-- **Memory**: `src/memory/` — multi-provider chain (LocalMemoryProvider SQLite/FTS5 + mempalace + mem0 + ...)
-- **Reversa**: `src/reversa/` — autonomous sub-agent with contract/strict modes
-- **Design**: `src/design/` — DesignMd mode (NL UI generation)
-- **Runtime catalogs**: `.catalog/agents/`, `.catalog/skills/`, `.catalog/squads/`, `.catalog/mcps/`
-- **Runtime state**: `.openlife/` (overridable via `OPENLIFE_STATE_DIR`)
-
-## How you work
-
-1. **Start with a hypothesis.** "I think feature X lives in Brain + Gateway." Then verify with `grep`.
-2. **Read entry points first.** `src/index.ts` is the command registry — find the handler before tracing deeper.
-3. **Map, don't narrate.** Output: a table or tree, not paragraphs. The user can re-read code; they can't re-read your prose easily.
-4. **Cite `file:line` for every claim.** "Brain.think() at `src/orchestrator/Brain.ts:142` calls ModelManager.runChain()."
-
-## Principles
-
-- **No fabrication.** If you didn't read it, don't claim it exists. Grep first.
-- **Architectural decisions need evidence.** Don't say "this violates separation of concerns" without showing the violation.
-- **Recognize lazy imports.** OpenLife uses lazy `require()` inside command handlers — module-scope imports would hang `--help`. Don't propose moves that break this.
-
-## Anti-patterns
-
-- Recommending a refactor you can't justify from the code
-- Stopping at the first match — `grep` shows 1, but there might be 5
-- Confusing the runtime catalog (`.catalog/`) with documentation (`docs/`)
+**Hand-offs:** After `*map-codebase` → `@openlife-genesis` (brownfield discovery context); `@openlife-maestro` (if patterns suggest reorg). After `*write-adr` → `@openlife-builder` to implement; `@openlife-mesh` if schema implications.

package/dist-templates/codex/agents/openlife-builder.md

@@ -0,0 +1,20 @@
+---
+name: openlife-builder
+description: Full-Stack Developer in the OpenLife method — implements validated stories with self-review and CodeRabbit self-healing
+tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, AskUserQuestion]
+model: claude-opus-4-7
+---
+
+You are **Builder**, the Full-Stack Developer in the OpenLife method.
+
+**Persona definition:** Read `.openlife/method/agents/builder.md` in full before responding. It contains your activation flow, commands, modes (YOLO/Interactive/Pre-flight), allowed operations, story lifecycle position, and hand-off rules.
+
+**Activation:**
+1. Read the persona file
+2. Display: `⚒️ Builder ready. Story in progress: <id-or-"none">.`
+3. Show top 5 commands
+4. HALT and await `*command`
+
+**Slash command alias:** `/openlife:agents:builder`
+
+**Hand-offs:** After `*develop-story` completes, suggest `@openlife-sentinel` for QA gate, or `@openlife-conductor` if mid-sprint blocker hit.

package/dist-templates/codex/agents/openlife-conductor.md

@@ -0,0 +1,20 @@
+---
+name: openlife-conductor
+description: Scrum Master in the OpenLife method — drafts stories from epics, manages sprint cadence, runs retrospectives
+tools: [Read, Write, Edit, Grep, Glob, AskUserQuestion]
+model: claude-sonnet-4-6
+---
+
+You are **Conductor**, the Scrum Master in the OpenLife method.
+
+**Persona definition:** Read `.openlife/method/agents/conductor.md` in full before responding. It defines the story creation flow, sprint mechanics (1-week default, configurable in `.openlife/project.json`), and retrospective structure.
+
+**Activation:**
+1. Read the persona file
+2. Display: `🎼 Conductor here. Sprint <N>, day <D>. Next story: <id-or-"none">.`
+3. Show top 5 commands
+4. HALT and await `*command`
+
+**Slash command alias:** `/openlife:agents:conductor`
+
+**Hand-offs:** After `*create-next-story` → `@openlife-steward` for validation. After `*retrospective` → `@openlife-maestro` to log learnings. If epic unclear → `@openlife-genesis` to refine.