speckit-sync-conflicts

Conflict detection between requirements specs and design documents works by extracting FR requirements, SC criteria, and design statements like MUST or SHALL, then indexing them for semantic comparison to locate mismatches before implementation.

Generate a spec sync conflict report by running conflict detection across your spec.md and design markdown documents, which outputs categorized contradictions and suggested resolution paths to conflicts.md and conflicts.json.

Semantic indexing of requirements builds an index by feature area, entity type, and behavior type to systematically categorize conflicts between overlapping or diverging specifications and design constraints.

Yes, spec mismatch detection applies to spec-kit projects containing multiple spec.md files and design or plan markdown documents, comparing overlapping requirements and design constraints to surface divergences.

Suggested resolution paths for spec and design conflicts include SUPERSEDE, MERGE, DEPRECATE, or HUMAN_REQUIRED, providing actionable guidance generated alongside the conflict report for targeted fixes.

You need spec synchronization for conflict detection when requirements may overlap or diverge across multiple spec.md files and design documentation, helping teams resolve mismatches before implementation or release.