Files
msd-core/get-shit-done/workflows/discuss-phase/modes/chain.md
Tom Boucher 48824f258c fix(#444): resolver preamble checks repo-local .claude install path (#476)
The gsd_run resolver preamble now probes
<repo-root>/.claude/get-shit-done/bin/${_GSD_SHIM_NAME} as the second
check — immediately after the existing get-shit-done/bin/ check and
before command -v / $HOME/.claude fallbacks. This covers the install
layout produced by npx @opengsd/get-shit-done-redux@latest --claude --local.

A _GSD_RUNTIME_ROOT variable is introduced to bind the repo-root
expression once and reuse it for both checks without repeating the
git rev-parse subshell.

76 workflow files regenerated via node scripts/sync-runtime-launcher.cjs.
All parity, size-budget, and new regression tests pass.

Co-authored-by: CI Rebase Check <ci@gsd-redux>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-29 17:12:54 -04:00

4.9 KiB

--chain mode — interactive discuss, then auto-advance

Lazy-loaded. Read this file from workflows/discuss-phase.md when --chain is present in $ARGUMENTS, or when the parent's auto_advance step needs to dispatch to plan-phase under --auto.

Effect

  • Discussion is fully interactive — questions, gray-area selection, and follow-ups behave exactly the same as default mode.
  • After discussion completes, auto-advance to plan-phase → execute-phase (same downstream behavior as --auto).
  • This is the middle ground: the user controls the discuss decisions, then plan and execute run autonomously.

auto_advance step (executed by the parent file)

  1. Parse --auto and --chain flags from $ARGUMENTS. Note: --all is NOT an auto-advance trigger — it only affects area selection. A session with --all but without --auto or --chain returns to manual next-steps after discussion completes.

  2. Sync chain flag with intent — if user invoked manually (no --auto and no --chain), clear the ephemeral chain flag from any previous interrupted --auto chain. This does NOT touch workflow.auto_advance (the user's persistent settings preference):

_GSD_SHIM_NAME="gsd-tools.cjs"; _GSD_RUNTIME_ROOT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"; GSD_TOOLS="${_GSD_RUNTIME_ROOT}/get-shit-done/bin/${_GSD_SHIM_NAME}"; if [ -f "$GSD_TOOLS" ]; then gsd_run() { node "$GSD_TOOLS" "$@"; }; elif [ -f "${_GSD_RUNTIME_ROOT}/.claude/get-shit-done/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="${_GSD_RUNTIME_ROOT}/.claude/get-shit-done/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; elif command -v gsd-tools >/dev/null 2>&1; then GSD_TOOLS="$(command -v gsd-tools)"; gsd_run() { "$GSD_TOOLS" "$@"; }; elif [ -f "$HOME/.claude/get-shit-done/bin/${_GSD_SHIM_NAME}" ]; then GSD_TOOLS="$HOME/.claude/get-shit-done/bin/${_GSD_SHIM_NAME}"; gsd_run() { node "$GSD_TOOLS" "$@"; }; else echo "ERROR: gsd-tools.cjs not found at $GSD_TOOLS and gsd-tools is not on PATH. Run: npx -y @opengsd/get-shit-done-redux@latest --claude --local" >&2; exit 1; fi if && ; then gsd_run query config-set workflow._auto_chain_active false || true fi


3. Read consolidated auto-mode (`active` = chain flag OR user preference):
```bash
AUTO_MODE=$(gsd_run query check auto-mode --pick active 2>/dev/null || echo "false")
  1. If --auto or --chain flag present AND AUTO_MODE is not true: Persist chain flag to config (handles direct usage without new-project):

    gsd_run query config-set workflow._auto_chain_active true
    
  2. If --auto flag present OR --chain flag present OR AUTO_MODE is true: display banner and launch plan-phase.

    Banner:

    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
     GSD ► AUTO-ADVANCING TO PLAN
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
    Context captured. Launching plan-phase...
    

    Launch plan-phase using the Skill tool to avoid nested Task sessions (which cause runtime freezes due to deep agent nesting — see #686):

    Skill(skill="gsd-plan-phase", args="${PHASE} --auto ${GSD_WS}")
    

    This keeps the auto-advance chain flat — discuss, plan, and execute all run at the same nesting level rather than spawning increasingly deep Task agents.

  3. Handle plan-phase return:

    • PHASE COMPLETE → Full chain succeeded. Display:
      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
       GSD ► PHASE ${PHASE} COMPLETE
      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
      
      Auto-advance pipeline finished: discuss → plan → execute
      
      /clear then:
      
      Next: /gsd:discuss-phase ${NEXT_PHASE} ${WAS_CHAIN ? "--chain" : "--auto"} ${GSD_WS}
      
    • PLANNING COMPLETE → Planning done, execution didn't complete:
      Auto-advance partial: Planning complete, execution did not finish.
      Continue: /gsd:execute-phase ${PHASE} ${GSD_WS}
      
    • PLANNING INCONCLUSIVE / CHECKPOINT → Stop chain:
      Auto-advance stopped: Planning needs input.
      Continue: /gsd:plan-phase ${PHASE} ${GSD_WS}
      
    • GAPS FOUND → Stop chain:
      Auto-advance stopped: Gaps found during execution.
      Continue: /gsd:plan-phase ${PHASE} --gaps ${GSD_WS}
      
  4. If none of --auto, --chain, nor config enabled: route to confirm_creation step (existing behavior — show manual next steps).