Oneshot Workflow Skill

VCS Provider

This skill uses VCS operations through Exarchos MCP actions (create_pr, merge_pr, etc.) when the synthesize path is taken. These actions automatically detect and route to the correct VCS provider (GitHub, GitLab, Azure DevOps). No gh/glab/az commands needed — the MCP server handles provider dispatch.

A lean, four-phase workflow type for changes that are too small to justify the full feature flow (ideate → plan → plan-review → delegate → review → synthesize → completed) but still deserve event-sourced auditability and a planning step. The workflow is direct-commit by default with an opt-in PR path; the choice between the two is resolved at the end of implementing via a pure event-sourced guard, not a heuristic.

Read this first if you have never run a oneshot: the workflow has a choice state at the end of implementing. Whether you land on completed (direct commit) or transition through synthesize (PR) is decided by two inputs: the synthesisPolicy set at init, and whether the