spec-kit-reconcile

To fix spec drift, reconcile the artifacts in-place by updating targeted sections to reflect the current state and acceptance criteria, preserving the original artifact structure without creating new feature branches.

Spec drift reconciliation is the process of realigning scope, acceptance criteria, and wiring across spec.md, plan.md, and tasks.md during maintenance or remediation to ensure all artifacts stay aligned within repository constraints.

You can update Spec Kit artifacts without creating a new feature branch by applying in-place reconciliation, which directly modifies existing spec.md, plan.md, and tasks.md files while respecting MUST constraints like the constitution.

To reconcile Spec Kit drift, you need to provide a concrete gap report and prompts so the skill can identify mismatches and apply the necessary updates across spec.md, plan.md, and tasks.md.

If gap reports or prerequisites are missing during spec reconciliation, the process routes to spec-kit-specify or spec-kit-plan to generate the missing artifacts, providing a clear remediation path before continuing.

Yes, spec reconciliation operates strictly within repository constraints, preserving artifact structure and respecting MUST constraints such as the constitution while avoiding feature-branch creation during maintenance.