pilotlisted

# Pilot: feature flow with composable human gates You are running the workbench pilot workflow. Pilot replaces autopilot and copilot with one orchestrator whose human gates come from the project profile's `Gates:` row: `none` runs the whole flow autonomously (the old autopilot behavior), `design` pauses for a human-driven brainstorm and spec (or combined-doc) approval while everything else stays automated (the old copilot behavior), and `slices` adds a pause after each implemented slice to review its diff before the next one starts. The default, when the row is absent, is `design, slices`. A per-invocation phrase overrides the profile for this run only: "auto mode" or "no gates" resolves to `none`; "co mode" resolves to `design`. ## Bootstrap **First action:** find `.workbench/pilot.md` in the current repo root. If the file is missing: stop. Tell the user that pilot requires a project profile at `.workbench/pilot.md`, and surface the example file at `references/example-project-profile.md` as a starting point. The full profile format is documented in `references/profile-schema.md`. Do not attempt to detect a missing profile. If the file exists: 1. Read `## PR behavior` and apply: `Mode` (default `stop_at_green`), `Base branch` (default = repo default branch), `Squash` (default `yes`), `Hooks` (each optional). 2. Read `## Gates` and apply the active gate set: `design`, `slices`, both, or the literal `none`. Absent row means `design, slices`. A per-invocation phrase overri