gspec-analyze

Cross-referencing multiple specification documents detects discrepancies by scanning all gspec files for overlapping functionality, constraints, or data models. It analyzes profile, stack, style, practices, architecture, research, and feature docs to surface substantive conflicts.

Resolving conflicts between overlapping software specifications involves proposing 2-3 resolution options per discrepancy and applying controlled in-place updates only after user approval. This guided reconciliation ensures the spec suite remains coherent without altering original document structures.

Yes, you can synchronize multiple specification files without creating new documents. The Skill performs controlled in-place updates on affected specs, preserving the original document structure while ensuring the entire spec suite remains in-sync after conflict resolution.

Cross-document validation for gspec specifications works by scanning all documents including profile.md, stack.md, and features/*.md to detect substantive inconsistencies. It reports each conflict and guides user-driven reconciliation to achieve a coherent spec set.

You need to run a specification conflict analysis when multiple specs describe overlapping functionality, constraints, or data models. It is required for cross-document validation, conflict reporting, and controlled in-place updates to maintain a coherent spec set.