v1.81.0 ·
Items a person must start
Autopilot builds whatever aidlc roadmap next names. The function behind it, pickNextAt in packages/cli/src/roadmap/next.ts, skips only bad ranks, promoted items and blocked items. Nothing kept autopilot off an item that needed a person. The only way around it was to keep the item out of the backlog or rank it below everything autopilot would reach, and both distort the backlog.
The pieces were nearly there. The project declares run in roadmap.item_fields, and backlog items already carried run: autopilot or run: attended. Nothing read it.
What changed
Roadmap items now say whether autopilot may build them alone, and autopilot obeys. A missing value means autopilot may build the item, so a repo that never sets the field sees no change. Any other value keeps autopilot off it.
aidlc roadmap next --autopilot leaves attended items out of the order and lists them as skipped, as attended or as bad-run for a malformed value, in --explain and --json. Plain aidlc roadmap next, the HTML board and the console still offer attended items to a person. Autopilot now picks with --autopilot and says left for a person (run: attended): <items>. If only attended items are ready, autopilot run --all finds nothing ready and ends. Triage proposes the run mode alongside the rank and asks for both in one question.
On this repo's backlog, autopilot's next pick moved from 20261008-blocking-actions-never-block.md (rank 3, attended) to 20261010-ci-infra-failure-reads-as-code-failure.md (rank 6, autopilot). It is a minor release for that reason: autopilot now skips items it used to start.
Why this way
I could have had autopilot filter the backlog's answer itself. Then "what should be built next?" would be answered in two places that could drift apart. So the one command that ranks the backlog gained a switch that asks for autopilot's view. The same switch lets a person see what autopilot would pick, and why it passed over the rest.
A missing value is permission and an unreadable value is not. The unattended reader treats a value nobody can parse as "keep out", because a typo must never be read as permission. A person still sees that item in their own list, with a warning to fix it.
The field is set in the same question that already asks for an item's rank during triage, and written as plain text. I added no command for it. A rank has a rule across items that a command needs to protect. A run mode has none.
What it does not do
It decides who may start an item. It does not make anyone work the attended ones. Those wait in the backlog until a person starts them.