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.