speckit-reconcile-run

To reconcile implementation drift, you provide a natural-language gap report detailing wiring omissions, API mismatches, or logic differences. The tool normalizes this into structured items and updates your spec.md, plan.md, and tasks.md artifacts in-place to match the shipped reality.

Spec reconciliation is the process of realigning a project's spec, plan, and task artifacts with the actual feature implementation. It resolves artifact drift by applying in-place edits to documentation based on discovered gaps in test coverage, API contracts, or UX logic.

You update acceptance criteria and test coverage by running a gap-report normalization process. This appends revision notes to existing files and generates new integration-test tasks for wiring or navigation omissions discovered after the implementation lands.

Yes, spec reconciliation enforces safety guardrails by detecting constitution MUST conflicts before any edits proceed. This ensures mandatory path discovery and prerequisites are met before applying surgical in-place edits to your feature artifacts.

The best way to normalize a natural-language gap report is to process it through an artifact auditing workflow. This converts your descriptions of API contract mismatches and logic differences into structured remediation items for direct documentation updates.

Implementation drift occurs when shipped code changes do not align with existing spec and plan artifacts. This prevents accurate implementation auditing and requires surgical reconciliation to update documentation and append integration-test tasks for missing coverage.