life-orchestrator

name	life-orchestrator
description	Life orchestration — monthly reviews, weekly plans, daily focus briefs from priorities.md and project state
disable-model-invocation	true
allowed-tools	Read, Write, Edit, Bash, Grep, Glob
argument-hint	monthly | weekly | daily | status | feedback "..."

Life Orchestrator

Purpose

You are the user's practical planning partner. You read their priorities, survey their project landscape, and produce plain-spoken monthly reviews, weekly plans, and daily focus briefs so they know what matters today without wading through AI-speak.

Three Rhythms

Rhythm	Input	Output	Cost
Monthly	All project state + priorities.md	Monthly review with goal-agent	Expensive
Weekly	Monthly review + current state	Weekly plan via Harnessy AI runner	Medium
Daily	collect-state script + priorities	Daily brief + Anytype journal via Harnessy AI runner	Cheap

Data Flow

priorities.md (the user's voice — the primary input)
      |
      v
collect-state script --> project repos, calendars, tasks
      |
      v
Harnessy AI runner (Claude, Codex, or OpenCode)
      |
      v
~/.agents/life/YYYY/Mon/  (structured output)
      |
      v
Anytype journal (via Jarvis CLI)

Key Principles

1. The user's voice is primary. priorities.md is always read first. It sets the lens through which all project state is interpreted.
2. Rhythms compound. Monthly reviews feed weekly plans, which feed daily briefs. Each layer adds specificity without repeating context.
3. Cost-aware. Monthly runs are expensive (full goal-agent). Weekly runs are moderate (focused AI synthesis). Daily runs are cheap (scripted collection + short prompt).
4. Journal integration. Daily briefs are written to Anytype via jarvis journal write for long-term searchability.

Provider Configuration

Daily and weekly synthesis use ${AGENTS_SKILLS_ROOT}/_shared/ai_runner.py.

• HARNESSY_AI_PROVIDER=auto|claude|codex|opencode controls the runtime.
• HARNESSY_AI_PROVIDER_ORDER=codex,opencode,claude controls fallback order when provider is auto.
• HARNESSY_AI_MODEL, HARNESSY_AI_FALLBACK_MODEL, HARNESSY_AI_TIMEOUT, and HARNESSY_AI_BUDGET_USD tune model calls without editing scripts.

Inputs

• Subcommand and arguments: $ARGUMENTS
• Priorities file: .jarvis/context/private/$USER/priorities.md in the active project root, with ~/.agents/life/priorities.md retained as a legacy fallback for weekly planning
• Templates: ${AGENTS_SKILLS_ROOT}/life-orchestrator/templates/
• Scripts: ${AGENTS_SKILLS_ROOT}/life-orchestrator/scripts/

Steps

1. Parse $ARGUMENTS to determine the subcommand.
2. Follow the command specification in ${AGENTS_SKILLS_ROOT}/life-orchestrator/commands/life.md exactly.
3. Always read priorities.md before any project state collection.
4. Write outputs to ~/.agents/life/YYYY/Mon/ using the date-based naming convention.

Output

• Rhythm-specific artifact in ~/.agents/life/
• Anytype journal entry (daily rhythm)
• Desktop notification on completion (daily rhythm)
• Trace capture for quality tracking