Automation Level Behavior Guide

Reference for how commands and skills should adjust interaction ceremony based on the active automation level. The big-picture description of each level (and how to switch) is in PROJECT-ORCHESTRATION-HANDBOOK.md §7.1; this doc is the per-decision behavior table. Warp-drive’s level-specific behavior is in the handbook §7.2 and warp-drive-guide.md.

Detection

Read .claude/settings.local.json in the project directory. Look for _automation.active_level (1, 2, or 3). If not found or the file doesn’t exist, default to Level 1.

Level Principles

Level 1 — Supervised (default)

  • Ask before every decision
  • Show all options with explanations
  • Wait for explicit confirmation before acting
  • This is identical to pre-automation behavior

Level 2 — Trusted Dev

  • Auto-proceed on safe, inferrable, or reversible decisions
  • Still confirm destructive operations (force push, delete, overwrite)
  • Still ask for subjective content (summaries, descriptions, priorities)
  • Show each auto-decision inline as it happens

Level 3 — Autonomous

  • Minimize prompts — only stop for destructive ops or subjective content
  • Auto-infer from git context, branch names, file paths, commit history
  • Batch auto-decisions into a summary rather than inline notifications
  • Ask for: rebase conflicts, subjective writing, destructive operations

Transparency Format

Commands must show what was auto-decided so the user stays informed.

Level 2 — inline per decision:

> Auto (L2): Branch type set to `tooling/` (inferred from .claude/ changes)
> Auto (L2): Stashed 2 uncommitted files

Level 3 — batched summary:

> Auto (L3) decisions:
>   - Branch type: `tooling/` (inferred from .claude/ changes)
>   - Stashed 2 uncommitted files
>   - Branch name: `tooling/automation-behavior`

Decision Classification

CategoryL1L2L3
Safe + inferrableAskAuto, showAuto, show
Reversible actionAskAuto, showAuto, show
Subjective contentAskAskAsk
Destructive operationAskAskAsk
Push to remoteAskConfirmAuto (except main/master)
Conflict resolutionAskAskAsk
Requirement/AC trackingAskAuto-update, showAuto-update, show
Documentation housekeepingAskAuto-update, showAuto-update silently
Warp-drive continue to next taskAskAskAuto-continue, log
Warp-drive plan reviewAskAskAuto-proceed, log