autopilotlisted

# autopilot — the entry point for a whole unattended run This skill orchestrates the complete run. It sequences three phase skills and adds the up-front kickoff. It does not duplicate their content. ## Kickoff Do this once before triage: 1. **Establish the resource picture.** Find out what you actually have to spend — time, a request or token quota, a cost cap if one exists at all — by checking, not by assuming. Many setups have no cap, and in those the answer is simply "no limit to plan around". Never conclude you are blocked without looking: if the user's prompts are being answered, the pipe is working. 2. **Warm any delegate lanes.** A delegate is not necessarily one thing: local inference and free/cheap remote APIs are two independent lanes, and a run can use either or both — including in parallel, when independent items are ready at the same time and each lane has spare capacity. Start whichever lane(s) exist in the background so the first delegation is not a cold start. Capture whatever address, port, or endpoint each warm-up reports. 3. **Ask blocking questions about THE RUN — and only about the run.** Scope, and permission for any push, publish, or confirmation-gated action. Ask for the **ship-loop depth** as one question — cleared through push, through tag, or through release — rather than a bare yes to “may you push”, because the loop's later steps publish and a run with nobody present cannot widen its own permission when it reaches one. Do not stop for those ag