autonomous

STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes tokens. Begin executing Step 0 immediately.

/pbr:autonomous — Hands-Free Multi-Phase Execution

References: @references/questioning.md, @references/ui-brand.md

Step 0 — Immediate Output

Before ANY tool calls, display this banner:

╔══════════════════════════════════════════════════════════════╗
║  PLAN-BUILD-RUN ► AUTONOMOUS MODE                           ║
╚══════════════════════════════════════════════════════════════╝

Then proceed to Step 1.

---

Step 1: Config Gate and Parse Arguments

1. Read .planning/config.json. Check workflow.autonomous — if false or missing, display:

Autonomous mode is disabled.

Enable with: /pbr:config set workflow.autonomous true

Stop immediately. Do NOT proceed.

1. Parse $ARGUMENTS:

Argument	Meaning	Default
--from N	Start from phase N	Current phase from STATE.md
--through N	Stop after phase N	Last phase in current milestone
--speculative-depth N	How many phases ahead to plan speculatively	From config workflow.speculative_depth (default 2)
--dry-run	Show which phases would execute without doing anything	Off

1. Determine speculative planning settings:

   • Read workflow.speculative_planning from config — if false, speculative depth = 0
   • Read workflow.speculative_depth from config (default: 2)
   • If --speculative-depth N provided, override config value
   • Store as speculativeDepth for use in Step 3

2. Read gates.checkpoint_auto_resolve from config (default: "none"). Values:

   • "none": STOP on all checkpoints (user must resolve)
   • "verify-only": Auto-resolve checkpoint:human-verify (proceed after confidence-gate passes), STOP on checkpoint:human-action
   • "verify-and-decision": Auto-resolve verify + decision checkpoints, STOP on checkpoint:human-action
   • "all": Auto-resolve all checkpoints (dangerous — only for fully automated pipelines) Store as checkpointResolveLevel for use in Step 3c.

3. Read .planning/STATE.md to determine current phase (used as default for --from).

4. Read .planning/ROADMAP.md to build phase list for current milestone.

5. CRITICAL (hook-enforced): Write .active-skill NOW. Write .planning/.active-skill with the content autonomous using the Write tool. This registers the autonomous session with the workflow enforcement hooks. Child Skill() calls (plan, build, review) will overwrite this with their own skill name during execution and should restore or re-write it — but the orchestrator owns the initial write and final cleanup.

6. Filter to phases from --from through --through that are not yet complete.

7. If no phases to execute, display: "All phases in range are complete." and stop.