autonomous

<objective> Execute all remaining milestone phases autonomously. For each phase: discuss → plan → execute. Pauses only for user decisions (grey area acceptance, blockers, validation requests).

Uses ROADMAP.md phase discovery and Skill() flat invocations for each phase command. After all phases complete: milestone audit → complete → cleanup.

A cataloged external skill whose triggers match the phase scope is auto-inserted for the executor only when the structural trust gate allows it (ephemeral, logged in the run output and the pin record, released after the phase).

Creates/Updates:

• .planning/STATE.md — updated after each phase
• .planning/ROADMAP.md — progress updated after each phase
• Phase artifacts — CONTEXT.md, PLANs, SUMMARYs per phase

After: Milestone is complete and cleaned up. </objective>

<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/autonomous.md @${CLAUDE_PLUGIN_ROOT}/references/ui-brand.md </execution_context> <context> Optional flags: - `--from N` — start from phase N instead of the first incomplete phase. - `--to N` — stop after phase N completes (halt instead of advancing to next phase). - `--only N` — execute only phase N (single-phase mode). - `--interactive` — run discuss inline with questions (not auto-answered), then dispatch plan→execute as background agents. Keeps the main context lean while preserving user input on decisions.

Project context, phase list, and state are resolved inside the workflow using init commands (bm-sdk query init.milestone-op, bm-sdk query roadmap.analyze). No upfront context loading needed. </context>

<process> Execute the autonomous workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/autonomous.md end-to-end. Preserve all workflow gates (phase discovery, per-phase execution, blocker handling, progress display). </process>