speckit-sync-conflicts

Detect contradictory requirements across specification and design documents.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-sync-conflicts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-sync-conflicts
Source: https://github.com/datamonsterr/mycoai_projects/tree/main/.agents/skills/speckit-sync-conflicts
Command: npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-sync-conflicts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface contradictions between specifications and design documents, enabling faster human resolution.

Core Features & Use Cases

  • Detect conflicts across specs, design docs, and plans
  • Build a semantic index of requirements and detect various conflict types (same feature with different behavior, obsolete constraints, scope overlap, implicit conflicts)
  • Generate structured conflict reports with suggested resolutions and an audit trail

Quick Start

Run the speckit-sync-conflicts command to scan specs and design documents for conflicts.

Frequently Asked Questions about speckit-sync-conflicts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect conflicts between design docs and specifications?

Spec conflicts are identified by analyzing multiple specification sources to detect contradictory requirements, constraints, and ownership. The analysis builds a semantic index to flag scope overlaps and obsolete constraints for human review.

What is the best way to find contradictory requirements across multiple design documents?

Finding contradictory requirements involves scanning design artifacts to detect conflicting behaviors for the same feature. The process identifies scope overlaps and implicit conflicts, then proposes resolution paths like merge, supersede, or deprecate.

Can I automatically generate a conflict report for outdated specification constraints?

Generating a conflict report for outdated constraints involves scanning specifications to detect obsolete constraints and scope overlaps. The output is a structured report with suggested resolutions and an audit trail for human review.

How do I resolve spec conflicts once they are detected?

Resolving detected spec conflicts involves applying proposed resolution paths such as supersede, merge, or deprecate. Conflicts that cannot be resolved automatically are flagged for human-required review and documented in a comprehensive conflict report.

Does this spec conflict detection work without external dependencies?

Spec conflict detection works without external dependencies by independently analyzing specification sources and design artifacts. It builds a semantic index to detect contradictory requirements, constraints, and ownership, generating a comprehensive conflict report.