pibun: Skill for Claude Code

Autopilot Execute

You are running unattended. No human is present. Be fully autonomous. Do not ask questions. Do not wait for confirmation. Make decisions and log them.

Step 0 — Read Project Config

Read autopilot.config in the project root. It defines:

• BUILD_CMD — the command to verify the project builds (may chain multiple checks)
• PROJECT_DIR — the directory containing the project source (. for monorepos)

If autopilot.config does not exist, look for a package.json and use bun run typecheck as the default build command in the current directory.

Step 1 — Orient (mandatory, fast)

Read these files in this order:

1. CLAUDE.md — Project identity, current state, commands, conventions
2. .plan/PLAN.md — Find current phase and next uncompleted item
3. .plan/MEMORY.md — Absorb all shared context, decisions, gotchas
4. .plan/DRIFT.md — Check for spec changes

If CLAUDE.md references additional files to read (AGENTS.md, CONVENTIONS.md, etc.), read those too — but be fast. Orientation should take seconds, not minutes.

Then print exactly one status line:

📍 Phase {N} — {Phase Name} | 📋 Next: {N.X} — {Description} | 📝 {count} items left in phase

Step 2 — Scope

Look at the next unchecked item in the current phase.

Sizing judgment:

• If the item is small (create a helper function, add a config value, write a type definition) → combine it with the next 1-2 unchecked items in the same phase
• If the item is medium (build a module, implement a feature, create a component) → do just that item
• If the item is large (complex multi-file feature, integration work) → do just that item, potentially noting sub-progress
• If it's a verification item (e.g., "verify all endpoints work", "run full test suite") → run the checks, report results
• If it's a CREATE TASKS item (meta-task) → read the data source, generate the plan items, insert them, then EXIT immediately

Announce your scope:

🎯 This iteration: {N.X} — {Description} [and {N.Y} if combining]