ferrox-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. **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/ferrox-core/workflows/autonomous.md @~/.claude/ferrox-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 `ferrox-plan-review-convergence` instead of plain `ferrox-plan-phase`. Requires `workflow.plan_review_convergence=true`. - `--cross-ai` — compatibility alias for `--converge`. When `--converge` or `--cross-ai` is set, reviewer selector flags supported by `ferrox-plan-review-convergence` may be passed through: `--codex`, `--gemini`, `--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 (`ferrox-tools query init.milestone-op`, `ferrox-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>