blueprint-autopilotlisted

# blueprint-autopilot The level-2 executor of the ADR-0020 autonomy model: runs due **agent-judgment** maintenance tasks and (optionally) drafts work-order proposals — quietly, with a one-line receipt. The inverse of `/blueprint:execute`: no menus, no questions, act then report. ## When to Use This Skill | Use this skill when... | Use /blueprint:execute instead when... | |------------------------|----------------------------------------| | The session-start drift nudge says blueprint tasks are due (`→ /blueprint:autopilot`) | The user wants an interactive "what's next?" menu | | `automation.autonomy_level` ≥ 2 and ambient maintenance should just happen | The user wants to drive each action themselves | | A work-order proposal should be drafted from a ready PRP without interrupting the user | The user wants to create a real work order now (`/blueprint:work-order`) | ## Context - Automation config: !`bash ${CLAUDE_SKILL_DIR}/../../scripts/get-automation-config.sh` - Due tasks (report mode, no writes): !`bash ${CLAUDE_SKILL_DIR}/../../scripts/blueprint-autorun.sh --report` ## Execution Execute this autopilot pass: ### Step 1: Gate on autonomy level Read `AUTONOMY_LEVEL` from the Context automation config. If it is **below 2**, stop immediately with the single line `Autopilot inactive (autonomy_level N) — raise automation.autonomy_level in docs/blueprint/manifest.json to enable.` Nothing else. Also stop (silently, one line) when `BLUEPRINT_AUTORUN_DISABLE=1` is set in th