gsd-autonomous

<arguments>$ARGUMENTS</arguments>

The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.

<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.

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/gsd-core/workflows/autonomous.md @/.claude/gsd-core/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. - `--converge` — run each phase's planning step through `gsd-plan-review-convergence` instead of plain `gsd-plan-phase`. Works even when `workflow.plan_review_convergence` is `false` — the explicit flag overrides the gate; the gate (`workflow.plan_review_convergence=true` enables it) governs the standalone `gsd-plan-review-convergence` command. Without the flag, planning runs `gsd-plan-phase`. - `--cross-ai` — compatibility alias for `--converge`.

When --converge or --cross-ai is set, reviewer selector flags supported by gsd-plan-review-convergence may be passed through: --codex, --claude, --opencode, --ollama, --lm-studio, --llama-cpp, --all, and --max-cycles N.

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

<process> Execute end-to-end. Preserve all workflow gates (phase discovery, per-phase execution, blocker handling, progress display). </process>