speckit.spex-collab.reconcile

Reconcile Implementation with Revised Spec

After a spec revision changes the task list, this command scans the existing codebase to determine which tasks are already satisfied, which need rework, and which are new. It produces a reconciled tasks.md where /speckit-implement can pick up only the delta.

Ship Pipeline Guard

If .specify/.spex-state exists with mode: "ship", return immediately.

Resolve Context

PREREQ=$(.specify/scripts/bash/check-prerequisites.sh --json --paths-only 2>/dev/null)
FEATURE_DIR=$(echo "$PREREQ" | jq -r '.FEATURE_DIR')
BRANCH=$(git branch --show-current)

Verify required artifacts:

[ -f "${FEATURE_DIR}/spec.md" ] || { echo "ERROR: No spec.md"; exit 1; }
[ -f "${FEATURE_DIR}/tasks.md" ] || { echo "ERROR: No tasks.md"; exit 1; }
[ -f "${FEATURE_DIR}/plan.md" ] || { echo "ERROR: No plan.md"; exit 1; }

Detect Existing Implementation

Check whether implementation work already exists on this branch:

# Count non-spec commits on the feature branch
IMPL_FILES=$(git diff --name-only main...HEAD 2>/dev/null | grep -v '^specs/' | grep -v '^brainstorm/' | grep -v '^\.' | head -50)
IMPL_FILE_COUNT=$(echo "$IMPL_FILES" | grep -c . 2>/dev/null || echo 0)

If no implementation files are found (IMPL_FILE_COUNT is 0):

No implementation files detected on this branch.
Nothing to reconcile. Run /speckit-implement to start fresh.

Return.

Read Artifacts

1. tasks.md: Parse the full task list. Extract each task's:

   • ID (e.g., T01, 1.1)
   • Status ([ ] or [X])
   • Description
   • File paths mentioned in the task
   • Phase assignment
   • Parallel marker [P] if present

2. plan.md: Read for architecture context, file structure, and module organization to understand what each task produces.

3. spec.md: Read for requirements to understand what "satisfied" means for each task.

Analyze Each Task Against Existing Code

For each task in tasks.md that is currently [ ] (not yet marked complete):