run

Autobuild - Run Orchestrator

Load and execute the autobuild skill for autonomous iteration orchestration.

Pre-flight install (MANDATORY, no asking)

Before invoking orchestrate, always run:

python3 -m pip install --user --upgrade stellars-claude-code-plugins 2>&1 | tail -1
LIB=$(python3 -c "import importlib.metadata as m;print(m.version('stellars-claude-code-plugins'))" 2>/dev/null) || { echo "FATAL: toolkit unavailable"; exit 1; }
PLUG=$(grep -m1 '"version"' "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null | cut -d'"' -f4)
OLDER=$(printf '%s\n%s\n' "$LIB" "$PLUG" | sort -V | head -1)
[ -n "$PLUG" ] && [ "$LIB" != "$PLUG" ] && [ "$OLDER" = "$LIB" ] && { echo "STALE: library $LIB older than plugin $PLUG - refusing to run on an outdated CLI; re-run the upgrade"; exit 1; }
echo "toolkit $LIB"

Run the CLI without touching the caller's project. The gate above puts it on PATH, so the bare command name is the whole invocation. uv run instead resolves whatever project the working directory sits in and writes uv.lock and .venv into it, so if you reach for uv pass --no-project (uv run --no-project <cli> ...) - it skips project discovery, leaves the tree untouched and still finds the same PATH binary. --no-sync and --frozen are not substitutes; both still create .venv.

The upgrade always runs - a stale-but-importable install is exactly the failure this gate prevents, and the reinstall also repairs a stale shim on PATH whose package is uninstalled in the active Python.

Startup Sequence

When the user asks to run an improvement cycle, execute these skills IN ORDER before starting the orchestrator:

1. program-writer - Generate PROGRAM.md from user's objective. Ask clarifying questions about scope, constraints, exit conditions. Do NOT proceed until user approves the program.

2. benchmark-writer - Generate BENCHMARK.md from the approved PROGRAM.md. Define score formula, direction (minimize/maximize), checklist sections, evaluation instructions. Do NOT proceed until user approves the benchmark.