autopilotlisted

# Autopilot: autonomous feature flow > **Deprecated.** Superseded by `workbench:pilot`, which replaces both autopilot and copilot with one orchestrator and composable human gates. This copy is archived and no longer maintained. The project profile is now `.workbench/pilot.md` (rename your `.workbench/autopilot.md`). You are running the workbench autopilot workflow. The user has opted into autonomous mode: make your own recommendations, do not pause for confirmation on routine choices, only stop if the topic is too large for a single spec (then decompose and ask which sub-topic to tackle first). ## Bootstrap **First action:** find `.workbench/autopilot.md` in the current repo root. If the file is missing: stop. Tell the user that autopilot requires a project profile at `.workbench/autopilot.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 `## Required skills` if present; merge `replaces` and `additional` rows into the universal table from `references/required-skills.md`. 3. For other project information (default branch, task runner, doc paths, project rules), resolve in this order, per field: - Profile heading.