a5eceb1faf
Extends the canonical runtime-launcher snippet with a third resolution arm
that probes $HOME/.claude/get-shit-done/bin/${_GSD_SHIM_NAME} between the
PATH check and the hard-error exit. Global Claude-Code installs (--claude
without --local) with no PATH wiring and no RUNTIME_DIR no longer hit the
hard-error path.
Resolution order: local/RUNTIME_DIR -> PATH -> ~/.claude/... -> hard error.
Propagated to 76 workflow .md files via sync-runtime-launcher.cjs. Parity
test (G) and bug-211 regression test (4 assertions) added.
3.3 KiB
--auto mode — fully autonomous discuss-phase
Lazy-loaded. Read this file from
workflows/discuss-phase.mdwhen--autois present in$ARGUMENTS. After the discussion completes, the parent'sauto_advancestep also readsmodes/chain.mdto drive the auto-advance to plan-phase.
Effect across steps
check_existing: if CONTEXT.md exists, auto-select "Update it" — load existing context and continue toanalyze_phase(matches the parent step's documented--autobranch). If no context exists, continue without prompting. For interrupted checkpoints, auto-select "Resume". For existing plans, auto-select "Continue and replan after". Log every decision so the user can audit.cross_reference_todos: fold all todos with relevance score >= 0.4 automatically. Log the selection.present_gray_areas: auto-select ALL gray areas. Log:[--auto] Selected all gray areas: [list area names].discuss_areas: for each discussion question, choose the recommended option (first option, or the one explicitly marked "recommended") without using AskUserQuestion. Skip interactive prompts entirely. Log each auto-selected choice inline so the user can review decisions in the context file:[auto] [Area] — Q: "[question text]" → Selected: "[chosen option]" (recommended default)- After all areas are auto-resolved, skip the "Explore more gray areas"
prompt and proceed directly to
write_context. - After
write_context, auto-advance to plan-phase viamodes/chain.md.
CRITICAL — Auto-mode pass cap
In --auto mode, the discuss step MUST complete in a single pass. After
writing CONTEXT.md once, you are DONE — proceed immediately to
write_context and then auto_advance. Do NOT re-read your own CONTEXT.md to
find "gaps", "undefined types", or "missing decisions" and run additional
passes. This creates a self-feeding loop where each pass generates references
that the next pass treats as gaps, consuming unbounded time and resources.
Check the pass cap from config:
_GSD_SHIM_NAME="gsd-tools.cjs"; GSD_TOOLS="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/get-shit-done/bin/${_GSD_SHIM_NAME}"; if [ -f "$GSD_TOOLS" ]; then 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
MAX_PASSES=$(gsd_run query config-get workflow.max_discuss_passes 2>/dev/null || echo "3")
If you have already written and committed CONTEXT.md, the discuss step is complete. Move on.
Combination rules
--auto --text/--auto --batch: text/batch overlays are no-ops in auto mode (no user prompts to render).--auto --analyze: trade-off tables can still be logged for the audit trail; selection still uses the recommended option.--auto --power:--powerwins (power mode generates files for offline answering — incompatible with autonomous selection).