speckit.status.check

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Goal

Provide a concise, actionable status report showing where the current feature stands in the speckit workflow pipeline. Detect which artifacts exist, assess their completeness, and recommend the next action.

Execution Steps

1. Detect Feature Context

Run .specify/scripts/bash/check-prerequisites.sh --json --paths-only from repo root. Parse JSON for:

• REPO_ROOT, BRANCH, FEATURE_DIR, FEATURE_SPEC, IMPL_PLAN, TASKS

For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

If the script fails (not on a feature branch), report:

Not on a feature branch. Current branch: <branch>
Run /speckit.specify to start a new feature.

Then stop.

2. Check Constitution

• Check if .specify/memory/constitution.md exists and is non-empty
• If it contains [PLACEHOLDER] or [ALL_CAPS_TOKEN] bracket tokens, mark as "Needs Update"
• Extract version from the **Version**: line if present

3. Scan Feature Artifacts

Run a single combined check for all artifacts. Use this exact script pattern (substituting the real FEATURE_DIR path):

d="<FEATURE_DIR>"
for f in spec.md plan.md tasks.md research.md \
         data-model.md quickstart.md; do
  [ -f "$d/$f" ] && echo "YES $f" || echo "NO  $f"
done
# Contracts directory (must be non-empty)
if [ -d "$d/contracts" ] && \
   [ -n "$(ls -A "$d/contracts" 2>/dev/null)" ]; then
  echo "YES contracts/ $(ls -1 "$d/contracts" | wc -l)"
else
  echo "NO  contracts/"
fi
# Checklists
if [ -d "$d/checklists" ]; then
  for c in "$d/checklists/"*.md; do
    [ -f "$c" ] || continue
    bn=$(basename "$c")
    t=$(grep -c '\[x\]\|\[X\]\|\[ \]' "$c" || echo 0)
    dn=$(grep -c '\[x\]\|\[X\]' "$c" || echo 0)
    echo "CL $bn $t $dn"
  done
else
  echo "NO  checklists/"
fi