← ClaudeAtlas

meridianexecutelisted

Use when you need Meridian to execution Engine.
mattjaikaran/meridian · ★ 1 · Data & Documents · score 73
Install: claude install-skill mattjaikaran/meridian
# /meridian:execute — Execution Engine Run plans via fresh-context subagents with TDD enforcement and 2-stage review. ## Arguments - `--phase <id>` — Execute specific phase (default: current phase) - `--plan <id>` — Execute single plan - `--wave <n>` — Execute specific wave only - `--no-review` — Skip 2-stage review (not recommended) - `--inline` — Execute in current context instead of subagent ## Procedure ### Step 1: Determine What to Execute ```bash PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c " import json from scripts.db import connect, get_db_path from scripts.state import compute_next_action, get_phase, list_plans conn = connect(get_db_path('.')) action = compute_next_action(conn) print(json.dumps(action, indent=2, default=str)) conn.close() " ``` If action is `execute` or `execute_plan`, proceed. Otherwise, show the required action. ### Step 2: Transition Phase to Executing ```bash PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c " from scripts.db import connect, get_db_path from scripts.state import transition_phase conn = connect(get_db_path('.')) transition_phase(conn, <phase_id>, 'executing') conn.close() " ``` ### Step 3: Execute Plans by Wave For each wave (starting from 1): #### 3a. Get plans for current wave ```bash PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c " import json from scripts.db import connect, get_db_path from scripts.state import get_plans_by_wave conn = connect(get