Ship Brief

Executes a Hamster Studio brief. Execution-only: the plan — parent tasks, subtasks, context — was generated upstream in Hamster Studio and synced into .hamster/. This skill schedules those existing tasks into parallel waves and executes them. It never generates, splits, or replans tasks on its own initiative — but it doesn't execute blindly either. Executors adapt to mechanical drift (documented as deviations) and escalate genuine plan defects as PLAN_ISSUE instead of implementing something known to be wrong; the orchestrator (and for scope changes, the user) decides how to proceed.

Project skills ARE loaded during execution: task-executors read .claude/skills/hamster-project-context/SKILL.md when it exists (generated by hamster sync; clients that discover .claude/skills/ expose it as the hamster-project-context skill), relevant project skills, and .hamster/ blueprints/methods. Execution-only restricts planning, not context.

Argument: "$ARGUMENTS"

Readiness

Before assuming a Hamster CLI, run this skill's bundled gate. Set SKILL_DIR to the absolute path of the directory holding the SKILL.md you just read — the shell's working directory is the user's project, not this skill — and keep the whole command on one line with its statements ;-separated, because some clients flatten a fenced block before running it. The else branch is the same gate inline, for clients that expose no readable path to the installed package.

Unix:

SKILL_DIR="<absolute path of the directory containing this SKILL.md>"; if [ -f "$SKILL_DIR/scripts/ensure-ready.sh" ]; then bash "$SKILL_DIR/scripts/ensure-ready.sh"; else export PATH="$HOME/.hamster/bin:$PATH"; if command -v hamster >/dev/null 2>&1 && { status_err="$(hamster --no-tui status 2>&1)"; printf '%s' "$status_err" | grep -q "Logged in" || { printf '%s\n' "$status_err" >&2; false; }; } && sync_err="$(hamster sync 2>&1)"; then echo READY; else [ -n "${sync_err:-}" ] && printf '%s\n' "$sync_err" >&2; echo SETUP_NEEDED; exit 1; fi; fi