@rasensio/aidlc-content 1.45.1 → 1.47.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc-content",
-  "version": "1.45.1",
+  "version": "1.47.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills/03-entry-point.md

@@ -49,6 +49,7 @@ Compose a short menu from the state. Include only the options that make sense:
 - **Answer pending questions** — when the pending-question count is above zero; show it and where they are (e.g. "2 questions waiting — `my-feature`, constitution update"). List this first among the roadmap and question entries: an unanswered question is work already blocked.
 - **Triage the inbox** — when `inbox/` is non-empty; show the count (e.g. "3 items awaiting triage"). List this above **Browse** — an untriaged submission is somebody waiting on a decision.
 - **Browse / promote the roadmap** — when any status directory outside `hold/` is non-empty; show counts per status (e.g. "3 inbox, 5 backlog, 1 in progress, 12 done").
+- **Work the backlog in the background** — when `backlog/` is non-empty; show the count (e.g. "5 ready in backlog — do the next n, or all").
 - **Show status** — when at least one instance exists.
 - **Review an artifact** — when at least one instance has a completed artifact.
 - **Help / getting started** — always.
@@ -68,6 +69,8 @@ If `.aidlc/state/` is empty or missing, offer just three options: start somethin
 | Triage the inbox | Follow the **aidlc-roadmap** skill (triage flow) |
 | Browse / promote the roadmap | Follow the **aidlc-roadmap** skill (browse/promote flow) |
 | Start a roadmap item in a new worktree | Follow the **aidlc-roadmap** skill (**Promote into a new worktree**). It ends by handing off to a new session; do not start the phase here |
+| Work the backlog in the background ("do the next 3 items", "do all the items") | Follow the **aidlc-autopilot** skill |
+| Stop autopilot | Follow the **aidlc-autopilot-stop** skill |
 | Show status | Summarize each instance from its state files — name, template, current phase, completion %, and whether it looks stalled. When the roadmap is non-empty, append the per-status counts (e.g. "roadmap: 3 inbox, 5 backlog, 12 done") |
 | Review an artifact | Follow the **aidlc-review** skill |
 | Help / getting started | Follow the **aidlc-getting-started** skill |

package/skills/84-autopilot.md

@@ -0,0 +1,44 @@
+---
+name: aidlc-autopilot
+description: Works the next backlog items in the background — "do the next 3 items" or "do all the items" — and reports how to watch and stop
+phase: implementation
+priority: 60
+trigger: When the user asks to do, work, build or ship the next n backlog items, or all of them, without supervising each one
+---
+# Autopilot
+
+## Purpose
+
+Turn "do the next 3 items" into one background run. The run builds each ready backlog item in its own worktree with an unattended agent, opens a pull request, waits for CI, merges, and runs the configured release step — one item at a time through the merge.
+
+The CLI does the work. This skill starts it and says how to watch and stop it. Do not build the items yourself in this session.
+
+## Instructions
+
+1. **Read the count.** "the next 3 items" → `--items 3`. "all the items", "the whole backlog" → `--all`. "the next item" → `--items 1`. If no count is given, ask once: how many items, or all?
+
+2. **Check it is set up.** Run `aidlc autopilot status`. If the user has never run setup, `run` refuses in step 3 and says so; then go to step 4.
+
+3. **Start the run.** From the project, run:
+   ```
+   aidlc autopilot run --items <n>
+   ```
+   or `aidlc autopilot run --all`. It returns at once. Do not wait for it, and do not poll it.
+
+4. **If it refuses:**
+   - *not set up* → tell the user to run `aidlc autopilot setup` in their own terminal. It asks which agent to use and what it may do; that choice is theirs, so do not pick it with flags on their behalf.
+   - *a run is already active* → report its pid and offer `aidlc autopilot stop` first.
+
+5. **Report**, in four short lines: what it is doing (how many items), the log file it printed, `aidlc autopilot status` to watch, and `/aidlc-autopilot-stop` (or `aidlc autopilot stop`) to stop.
+
+## What the run does on its own
+
+- Takes items in `aidlc roadmap next` order. Builds at most two at once, and never more than the count asked for.
+- Parks an item (moves it to `hold/` with a reason) when its agent stops short, when CI fails twice, or when it passes the cost cap.
+- Halts the merge queue when a merge or release step fails, and never retries it. A half-done release is for a person — `aidlc autopilot status` shows the error.
+- Ends when the asked-for items are each released or parked, or, with `--all`, when nothing is ready and nothing is in flight.
+
+## Exit Criteria
+
+- `aidlc autopilot run` has started a run, or its refusal has been reported with the one command that fixes it
+- The user knows where the log is, how to watch, and how to stop

package/skills/85-autopilot-stop.md

@@ -0,0 +1,28 @@
+---
+name: aidlc-autopilot-stop
+description: Stops the background autopilot run — nothing further is started, merged or released
+phase: implementation
+priority: 60
+trigger: When the user asks to stop, halt or pause autopilot or the background backlog run
+---
+# Stop Autopilot
+
+## Purpose
+
+Stop the background run in one step.
+
+## Instructions
+
+1. Run:
+   ```
+   aidlc autopilot stop
+   ```
+   No confirmation is needed: stopping changes nothing that cannot be resumed.
+
+2. Report what it printed: which run was stopped (its pid) or that none was active, and each agent still finishing. Agents already running are left to finish their current item; nothing new is started, merged or released.
+
+3. Say how to resume: `aidlc autopilot run --items <n>` (or `--all`) starts again and clears the stop.
+
+## Exit Criteria
+
+- The stop file exists and the user has been told what was stopped and how to resume