メニュー
Run in Claude Code to hand a specific bead to Antigravity. Emits a copy-paste prompt for the Antigravity 2.0 agent manager. Does NOT create branches or worktrees — the agent manager does that from the prompt text.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Security patterns, CSP nonces, input validation, auth checks, Supabase SSR patterns. Use when implementing authentication, forms, security features, or when user mentions security/validation/auth.
Use when running the superpowers plugin lifecycle inside PinPoint — brainstorming, writing-plans, subagent-driven-development, requesting/receiving-code-review, or finishing-a-development-branch — and when a superpowers step wants to merge a branch locally, remove a worktree by hand, run generic npm/pytest tests, dispatch subagents without a scale gate, or write a spec/plan from the read-only root. Also when deciding which bead field a spec, plan, acceptance criterion, or landing note belongs in.
Orchestrate parallel subagent work in git worktrees — task selection, end-to-end dispatch, monitoring, follow-up, and cleanup.
Full PR lifecycle for PinPoint — commit, push, CI monitoring, Copilot + human review handling (via MCP), readiness labeling, gate-enforced merge. Use when committing changes, opening PRs, watching CI, addressing review comments, or merging.
Per-PR /audit-override escape hatch for unrelated pnpm audit failures blocking CI Gate. Use when a PR's audit job goes red on a freshly-published advisory unrelated to the PR's own changes, or when explaining/debugging the /audit-override command.
Supabase/Postgres pooler and connection-string reference for PinPoint — Supavisor transaction vs session pooler, IPv4/IPv6, prepared statements, and the resolved PP-d8l8 silent-commit-loss incident. Use when touching src/server/db/**, scripts/migrate-production.ts, scripts/lib/pg-client.mjs, or any DB connection/pooler config.
| name | pinpoint-agy-dispatch |
| description | Run in Claude Code to hand a specific bead to Antigravity. Emits a copy-paste prompt for the Antigravity 2.0 agent manager. Does NOT create branches or worktrees — the agent manager does that from the prompt text. |
When to invoke: Tim says "dispatch this to Antigravity", "hand PP-xxx to agy", or "pick an agy-ready bead and send it to Antigravity."
Run in Claude Code (not in Antigravity). The output is a copy-paste prompt for the Antigravity 2.0 agent manager.
The Antigravity 2.0 agent manager derives the worktree name and branch name from the initial prompt text. A generic opening like "find an agy-ready bead and take it to review" produces a generic branch (e.g., agent-find-an-agy-ready). A specific imperative naming the bead produces a well-named branch (e.g., implement-pp-xxxx-fix-email-field).
This skill's primary job is to ensure the first line of the emitted prompt is always a specific imperative naming the bead.
If Tim gives you a bead ID: use it directly.
If no bead ID is given: run:
bd query "label=agy-ready AND status=open" --priority-max=2
Pick the top result by priority, then by ID (lexicographic tiebreak).
bd show <id>
Read: title, description, acceptance criteria, labels, all comments.
Verify agy-ready is present. If it is absent, stop and tell Tim:
"PP-xxx does not have the
agy-readylabel. Run thepinpoint-agy-triageskill to evaluate it before dispatching."
Detect agy-ui. Note whether the agy-ui label is present — this controls whether the UI-verification block is included in the emitted prompt.
Output the following fenced block for Tim to paste into the Antigravity 2.0 agent manager.
Critical formatting rule: the very first line must be a specific imperative naming the bead ID and a concise title. The agent manager uses this line to name the worktree and branch. Do not open with "find a bead", "work on an issue", or any generic sentence.
Prompt template (non-UI bead):
```
Implement <id>: <concise title from bead>
Bead: <id> — <full bead title>
Goal: <1–3 sentences in plain language describing what needs to change and why, derived from the bead description. No jargon. Write as if explaining to someone who hasn't read the bead.>
Follow the `pinpoint-agy-execute` skill starting at Step 1 — the bead ID is already specified, so skip the discovery query, but still run the Step 1 label-verification (`agy-ready`) and `agy-ui` detection. Then continue end-to-end (Step 2 claim onward).
Verification command: <exact command from the bead, e.g. `pnpm run check` or `pnpm exec playwright test e2e/foo.spec.ts --project=chromium`>
```
Prompt template (UI bead — agy-ui label present):
```
Implement <id>: <concise title from bead>
Bead: <id> — <full bead title>
Goal: <1–3 sentences in plain language describing what needs to change and why, derived from the bead description.>
Follow the `pinpoint-agy-execute` skill starting at Step 1 — the bead ID is already specified, so skip the discovery query, but still run the Step 1 label-verification (`agy-ready`) and `agy-ui` detection. Then continue end-to-end (Step 2 claim onward).
Verification command: <exact command from the bead>
UI verification (this is an `agy-ui` bead):
Before opening the PR (after Step 5, before Step 8): start Supabase (`supabase start`) and the dev server (`pnpm dev`) for this worktree. The assigned port is in `.env.local` and `.claude/launch.json`. Use `/browser` to open the app at that port and confirm: <paste acceptance criteria verbatim>.
If any fixes land after the first UI check (e.g. CI failures, before Step 10's label): re-run `/browser` to confirm the changes did not break the UI.
Note: `/browser` grants Chrome access only. You must start the stack manually before using it.
```
After the fenced block, add exactly one line:
Paste this into the Antigravity 2.0 agent manager to spawn a new agent. The branch name is derived from the first line.
If Tim asks you to also triage the bead first, load the pinpoint-agy-triage skill.