eforge-workflow

# /eforge:workflow Configure the eforge workflow preset for this project using the native Pi workflow wizard. Answers four questions to select one of five presets and writes the matching config keys to `eforge/config.yaml`. In Pi, this skill is backed by native select-overlay panels (`showSelectOverlay` / `showSearchableSelectOverlay`) for each question, providing a visual picker experience. The underlying preset logic and config keys are identical to the Claude Code `/eforge:workflow` skill. ## Commands - `/eforge:workflow` — auto-detects mode (init if not configured, reconfigure if already configured) - `/eforge:workflow:init` — always runs the full wizard from scratch - `/eforge:workflow:reconfigure` — shows current config summary before the wizard ## Four wizard dimensions The wizard asks four questions in sequence: ### 1. Development context (solo vs team) - **Solo** — you are the only developer merging to trunk - **Team** — multiple developers merge PRs; code review gates are active ### 2. Landing action (merge vs PR) - **Direct merge** (`merge`) — the artifact branch is merged directly into the base branch. Solo only (requires `build.allowLocalMergeToTrunk: true`). - **Pull request** (`pr`) — a GitHub PR is opened from the artifact branch. Required for team use. ### 3. Stacked PRs (git-spice or none) - **No stacking** — standard single-branch builds - **git-spice stacking** — each build PR targets the parent artifact branch. Requires git-spice and `git-spic...