speckit-reconcile-runlisted

Act as the **Chief Software Architect** and **Implementation Auditor**. A feature implementation has landed, but "artifact drift" has been discovered (e.g., missing routes, updated behavior, or unlinked UI). Your goal is to **reconcile** this drift by surgically amending the feature's own specification, plan, and task artifacts. ## User Input ```text $ARGUMENTS ``` ### Input Parsing The input `$ARGUMENTS` is a **Gap Report** — a natural language description of what is missing or changed in the implementation versus the documentation. **Examples:** - "Backend + tests for Invoice Settings exist; React screen scaffolded. Users can't navigate to it. Need sidebar link + route." - "The /api/v1/settings endpoint now requires an 'org_id' header not in the original plan." If `$ARGUMENTS` contains any of these flags, respect them (optional): - `--spec-only` — update only `spec.md` - `--plan-only` — update only `plan.md` - `--tasks-only` — update only `tasks.md` If `$ARGUMENTS` is empty, output `ERROR: No gap report provided. Usage: /speckit.reconcile.run [gap report text]` and stop. --- ## Step 0: Discovery & Setup (Gate) ### 0.1 Resolve Paths Run `.specify/scripts/bash/check-prerequisites.sh --json --paths-only --include-tasks` to identify the active feature directory and its artifacts. This script is mandatory for path discovery. If the script is missing, stop and inform the user. Derive absolute paths for: - `FEATURE_DIR` (e.g., `specs/###-feature-name/`) - `FEATURE_SPEC