/autopilot, Intake Pipeline

Orientation

Use Autopilot when:

• There are pending items in .planning/intake/
• You want to process intake items without manual orchestration
• The work is scoped and well-defined (Small or Medium complexity)

Do NOT use Autopilot for:

• Large, multi-session campaigns (use Archon)
• Parallel execution (use Fleet)
• Exploratory or open-ended work (use Marshal)

Protocol

Step 0: DELIVERY PREFLIGHT

When the user names a specific intake file or asks for "intake to PR", prefer the deterministic delivery preflight before freeform build work:

node scripts/deliver.js --intake .planning/intake/{item}.md

If no specific intake file is named, use:

node scripts/deliver.js --next

This selects the highest-priority pending item in .planning/intake/ and keeps the golden path deterministic.

This creates an active campaign with claimed scope, acceptance criteria, map context, and exit evidence rows, then marks the intake item in-progress. Continue from the created campaign with /do continue.

After build and verification, package the delivery before marking the campaign complete:

node scripts/package-delivery.js {campaign-slug}

If a PR exists, record the PR as the review target:

node scripts/package-delivery.js {campaign-slug} --pr https://github.com/{owner}/{repo}/pull/{number}

Step 1: SCAN

Read all files in .planning/intake/ and identify:

• status: pending → needs briefing
• status: briefed → ready to build
• status: approved → ready to build
• status: in-progress → check if stuck

Step 2: BRIEF (for pending items)

For each pending item: