Menu
Bootstrap the local development environment — checks prerequisites, starts Supabase, generates env files, launches dev servers
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Scaffold a new golden case for @butler/evals — validate and append the case to golden.jsonl, re-capture the baseline, and confirm the eval gate still passes. Use when a real agent failure or escaped bug should become a regression benchmark.
Work the Butler ready-for-agent issue queue in priority order — select the highest-priority unblocked issue (P0 > P1 > P2) and run /implement-issue on it, looping up to a per-run cap. Use ONLY when explicitly asked to "work the queue" / "implement the next issue(s)", or when fired by the scheduled routine. Do not auto-run.
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
End-to-end implementation of a GitHub issue — from reading the issue through TDD, code review, PR creation, CI monitoring, and merge. Use when the user says "implement issue
Phase 9 retrospective — read a window or set of recently-merged PRs, classify each harness/run finding with the eval-failure taxonomy, and append tagged learnings to docs/retro/learnings.md. Propose-only — writes ONLY under docs/retro/. Use when explicitly asked to "run a retrospective", "retro the last N PRs", or to review a batch of merged work for harness lessons. Do not auto-run.
Based on SOC occupation classification
| name | setup-dev |
| description | Bootstrap the local development environment — checks prerequisites, starts Supabase, generates env files, launches dev servers |
| disable-model-invocation | true |
Bootstrap everything needed to run Butler locally.
Butler requires Node.js 22+ (Wrangler dependency).
node --version
If below v22, stop and tell the user:
"Butler requires Node.js 22+. You're on [version]. Upgrade via
nvm install 22orvolta install node@22."
Local Supabase requires Docker.
docker info >/dev/null 2>&1
If Docker is not running, stop and tell the user:
"Docker is required for local Supabase. Start Docker Desktop and retry."
supabase start
This takes 1-2 minutes on first run (pulls Docker images). Extract the API URL and anon key from the output.
If supabase CLI is not installed, tell the user:
"Install the Supabase CLI:
brew install supabase/tap/supabase"
Create packages/frontend/.env with the values from supabase status:
supabase status -o json
Write to packages/frontend/.env:
VITE_SUPABASE_URL=<API URL from status>
VITE_SUPABASE_ANON_KEY=<anon key from status>
Do NOT commit this file — it is gitignored.
pnpm --filter @butler/shared build
pnpm --filter @butler/api dev &
pnpm --filter @butler/frontend dev &
curl http://localhost:8787/healthhttp://localhost:5173 in browserReport which services are running and any that failed.