workflows-setup

Set Up SDLC Delegated Workflows

Install Archon, build the sdlc-worker:base + sdlc-worker:full Docker images, and copy SDLC workflow templates and command prompts into the project.

Arguments

• (no argument) or --with-docker (default) — full setup: host Archon + workflows + Docker images. Recommended — this is the state in which /sdlc-workflows:workflows-run will actually work.
• --workflows-only — host Archon + workflows, no Docker build. Only use this when you know you already have sdlc-worker:base and :full from an earlier setup; a fresh project that picks this will see workflows-run fail at the first node with "image not found".
• --health-check — run diagnostic checks only (skip steps 1-8).

When --health-check is passed, skip steps 1-8 and go directly to step 9.

Default behaviour (no args) is --with-docker so a first-time user ends up in a working state without having to know which flags to pass.

Steps

1. Check if Archon is already installed

The upstream installer (curl -fsSL https://archon.diy/install | bash) drops the binary at ~/.bun/bin/archon because Archon is a Bun runtime app. On macOS this directory is not on the default shell PATH — so the binary exists but command -v archon returns nothing unless the user already has ~/.bun/bin on PATH.

Detect both cases, because "not on PATH" is very different from "not installed" (running the installer again is wasted work):

if command -v archon >/dev/null 2>&1; then
    ARCHON_STATUS=on-path
    ARCHON_BIN=$(command -v archon)
elif [ -x "$HOME/.bun/bin/archon" ]; then
    ARCHON_STATUS=installed-not-on-path
    ARCHON_BIN="$HOME/.bun/bin/archon"
else
    ARCHON_STATUS=missing
fi

If on-path: report and skip to step 3:

Archon is already installed and on PATH (version X.Y.Z).

If installed-not-on-path: the binary exists but won't be found by /sdlc-workflows:workflows-run. Do NOT re-run the installer — that's wasted work. Tell the user explicitly and have them choose: