autopilot

1# /autopilot — Intake Pipeline
2 
3## Orientation
4 
5Use Autopilot when:
6- There are pending items in `.planning/intake/`
7- You want to process intake items without manual orchestration
8- The work is scoped and well-defined (Small or Medium complexity)
9 
10Do NOT use Autopilot for:
11- Large, multi-session campaigns (use Archon)
12- Parallel execution (use Fleet)
13- Exploratory or open-ended work (use Marshal)
14 
15## Protocol
16 
17### Step 0: DELIVERY PREFLIGHT
18 
19When the user names a specific intake file or asks for "intake to PR", prefer
20the deterministic delivery preflight before freeform build work:
21 
22```bash
23node scripts/deliver.js --intake .planning/intake/{item}.md
24```
25 
26If no specific intake file is named, use:
27 
28```
29node scripts/deliver.js --next
30```
31 
32This selects the highest-priority pending item in `.planning/intake/` and keeps
33the golden path deterministic.
34 
35This creates an active campaign with claimed scope, acceptance criteria, map
36context, and exit evidence rows, then marks the intake item `in-progress`.
37Continue from the created campaign with `/do continue`.
38 
39After build and verification, package the delivery before marking the campaign
40complete:
41 
42```bash
43node scripts/package-delivery.js {campaign-slug}
44```
45 
46If a PR exists, record the PR as the review target:
47 
48```bash
49node scripts/package-delivery.js {campaign-slug} --pr https://github.com/{owner}/{repo}/pull/{number}
50```
51 
52### Step 1: SCAN
53 
54Read all files in `.planning/intake/` and identify:
55- `status: pending` → needs briefing
56…