speckit.spex-collab.reviewers

Generate REVIEWERS.md Review Guide

Ship Pipeline Guard

If .specify/.spex-state exists and its mode is "ship" or status is "running", skip REVIEWERS.md generation entirely and return immediately.

if [ -f ".specify/.spex-state" ]; then
  MODE=$(jq -r '.mode // empty' .specify/.spex-state 2>/dev/null)
  STATUS=$(jq -r '.status // empty' .specify/.spex-state 2>/dev/null)
  if [ "$MODE" = "ship" ] || [ "$STATUS" = "running" ]; then
    echo "Ship mode active, skipping REVIEWERS.md generation"
  fi
fi

If ship mode is detected, output nothing further and return. Do not generate or modify any files.

Extension Enabled Check

Verify spex-collab is active. If the extension directory does not exist, skip silently:

if [ ! -f ".specify/extensions/spex-collab/extension.yml" ]; then
  echo "spex-collab extension not found, skipping"
fi

If the extension is not found, return without generating REVIEWERS.md. Vanilla spec-kit behavior is preserved.

Resolve Spec Directory

Run the prerequisites script to locate the feature directory:

.specify/scripts/bash/check-prerequisites.sh --json --paths-only 2>/dev/null

Parse the JSON output to extract:

• FEATURE_DIR: absolute path to the spec directory (e.g., /path/to/specs/018-collab-extension)
• FEATURE_SPEC: path to spec.md

If resolution fails, inform the user and stop:

Cannot resolve spec directory. Are you on a feature branch?

Check for Existing REVIEWERS.md

REVIEWERS_PATH="${FEATURE_DIR}/REVIEWERS.md"
if [ -f "$REVIEWERS_PATH" ]; then
  echo "REVIEWERS.md exists, checking for code phase sections to preserve"
fi

If REVIEWERS.md already exists:

1. Read its content
2. Look for the first line matching ## Phase [0-9] (a code phase section heading)
3. If found: preserve everything from that line onwards (these are code phase sections from previous implementation phases). Only regenerate the spec sections above that boundary.
4. If no phase headings found: regenerate the entire file