pilot

Orchestrates end-to-end feature delivery from design through PR with configurable human gates.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/pgoell/pgoell-claude-tools --skill pilot-pgoell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot
Source: https://github.com/pgoell/pgoell-claude-tools/tree/main/plugins/workbench/skills/pilot
Command: npx skills add https://github.com/pgoell/pgoell-claude-tools --skill pilot-pgoell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping a feature end to end involves many coordinated steps: brainstorming, spec writing, planning, TDD implementation, docs updates, PR creation, and CI monitoring. Pilot automates this entire workflow as a single orchestrated run while letting teams configure exactly where humans stay in the loop. ## Core Features & Use Cases - Composable human gates: Configure design and slices gates in .workbench/pilot.md to pause for human-driven brainstorms, spec approvals, or per-slice diff reviews, or run fully autonomously with Gates: none. - Lane-based workflow sizing: Automatically triages work into quick, medium, or large lanes that skip or include spec and plan steps based on task scope. - Full PR lifecycle: Executes TDD-governed implementation with subagent dispatch, runs pre-PR verification, opens the PR with a reading guide, polls CI until green, and applies the configured merge policy (stop_at_green, automerge, or request_review). - Use Case: A developer asks to ship a new API endpoint. Pilot reads the project profile, confirms the lane, drives a brainstorm, writes spec and plan docs, implements slice by slice with tests, captures session learnings, opens the PR, and stops at green CI for manual merge. ## Quick Start Create a .workbench/pilot.md profile in your repo root, then ask the agent to ship your feature using the pilot workflow.

Frequently Asked Questions about pilot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a feature from design to pull request?

Create a `.workbench/pilot.md` profile in your repo root and invoke the pilot workflow. It runs ten steps covering triage, brainstorming, spec and plan writing, TDD implementation, docs updates, PR creation, and CI polling, pausing only at the gates you configure.

How do I configure human approval gates in an automated coding workflow?

Set the `Gates:` row in `.workbench/pilot.md` to `design`, `slices`, both, or `none`. The design gate pauses for human-driven brainstorm and spec approval; the slices gate pauses after each implemented slice for diff review. Per-invocation phrases like "auto mode" override the profile for one run.

Does the pilot workflow work with Codex as well as Claude Code?

Yes. The skill uses Claude Code tool names by default but ships a Codex adapter reference that maps each tool to its Codex equivalent, including a sequential main-session fallback when Codex lacks a subagent primitive.

What happens if the .workbench/pilot.md profile is missing?

Pilot stops immediately and tells the user a project profile is required, pointing to the bundled example profile as a starting point. It never attempts to detect or guess a missing profile.

Can pilot merge pull requests automatically?

Only when the profile explicitly sets `Mode: automerge`. The default `stop_at_green` mode never merges; it reports the PR URL once CI is green. A `request_review` mode marks the PR ready and posts a reviewer note instead.

What are the limitations of the pilot workflow?

Pilot requires a git repository with GitHub CLI access and depends on companion workbench skills for brainstorming, planning, TDD, and verification. Profiles can replace or add required skills but cannot remove the universal discipline floor, and hooks can never be skipped.