v2.3.0 ·
Doctor catches roadmap items filed in the wrong place
Autopilot builds whatever sits in backlog/, in rank order. That folder is supposed to mean "could start now". Nothing checked that it did.
In another project of mine, an item sat at rank 3 with a recommendation of "Do later, at Stage 1 after the Stage 0 gate". Autopilot would have offered it overnight. A project skill caught it by hand. The same project had 6 of 57 held items with no reason at all, so nobody could tell work that was parked from work that was dropped.
What doctor says now
aidlc doctor has three new findings. Each names the item and the fix.
- A
hold/item whose last hold entry does not sayparkedordeclined. Older forms likeParked:still count. - A
backlog/item whose summary recommendation opens with "Do later", "Not now" or "Don't do". The finding prints theaidlc roadmap park --itemcommand that moves it. - A parked item whose dependencies are all done, with at least one finished after it was parked. The fix is to look at it again.
On this repo the first run named three of the four backlog items. All three say "Do later" in their own summary. On the other project it named 19 held items: 6 with no reason, and 13 with older wording like "Merged into", "Not now:" or "Answered:".
Why it only reports
Doctor never moves an item or writes a reason. Parked and declined are opposite answers, and an invented decision reads exactly like a real one. So all three are report only, and none of them changes doctor's exit code.
The third check was the one I narrowed. The first draft fired on any parked item whose dependencies were all done. On this repo that would have flagged items I parked after their dependencies finished, waiting on things that are not dependencies, like someone outside my own projects asking. They would show up on every run, forever. Now a dependency has to finish after the park. Re-parking with a new reason clears the finding.
What it does not do
It cannot tell whether a free-text trigger like "before the second store" has happened. That still needs someone who knows the project.