speckit.spex.finish

Finish - Smoke Test, Squash, and Land the Code

Ship Pipeline Guard

If .specify/.spex-state exists and its status is running, this command is part of an autonomous pipeline. Check the ask field:

AUTONOMOUS_MODE=false
if [ -f ".specify/.spex-state" ]; then
  STATUS=$(jq -r '.status // empty' .specify/.spex-state 2>/dev/null)
  ASK=$(jq -r '.ask // "always"' .specify/.spex-state 2>/dev/null)
  if [ "$STATUS" = "running" ] && [ "$ASK" != "always" ]; then
    AUTONOMOUS_MODE=true
  fi
fi

In autonomous mode: suppress all interactive prompts, UNLESS running inside a worktree (IN_WORKTREE is true, detected in Phase 2). When in a worktree, always present the user with the action prompt (Phase 4) regardless of autonomous mode. Never auto-merge or auto-delete a worktree.

Argument Parsing

Parse the following flags from arguments:

• If --no-smoke-test is passed, set SKIP_SMOKE_TEST=true. This bypasses the smoke test gate unconditionally.

SKIP_SMOKE_TEST=false
for arg in "$@"; do
  case "$arg" in
    --no-smoke-test) SKIP_SMOKE_TEST=true ;;
  esac
done

Pre-Execution Checks

Check for extension hooks (before finish):

• Check if .specify/extensions.yml exists in the project root.
• If it exists, read it and look for entries under the hooks.before_finish key
• If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
• Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
• For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
  • If the hook has no condition field, or it is null/empty, treat the hook as executable
  • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
• Convert hook command names from dot notation to hyphen notation for slash command invocation (e.g., speckit.spex.smoke-test becomes /speckit-spex-smoke-test)
• Determine prompt behavior based on autonomous mode: when .specify/.spex-state exists with ask of smart or never, optional hooks execute without prompting (treated as mandatory). When ask is "always" or no state file exists, optional hooks prompt as normal.
• For each executable hook, output the following based on its optional flag:
  • Optional hook (optional: true) in interactive mode:

    ## Extension Hooks
    
    **Optional Pre-Hook**: {extension}
    Command: `/{command}`
    Description: {description}
    
    Prompt: {prompt}
    To execute: `/{command}`
    

  • Optional hook (optional: true) in autonomous mode (ask is smart or never): Treat as mandatory (auto-execute without prompting).
  • Mandatory hook (optional: false):

    ## Extension Hooks
    
    **Automatic Pre-Hook**: {extension}
    Executing: `/{command}`
    EXECUTE_COMMAND: {command}
    
    Wait for the result of the hook command before proceeding to Phase 1.
    

  • If a mandatory hook fails or is declined by the user, STOP. Output an error message indicating which hook failed and do NOT proceed to Phase 1.
• If no hooks are registered or .specify/extensions.yml does not exist, skip silently