openspec-harmonize-changes

Detect conflicting OpenSpec changes and generate a structured harmony report.

Updated Dec 8, 2025
One-click install
npx skills add https://github.com/open-platform-model/cli --skill openspec-harmonize-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-harmonize-changes
Source: https://github.com/open-platform-model/cli/tree/main/.claude/skills/openspec-harmonize-changes
Command: npx skills add https://github.com/open-platform-model/cli --skill openspec-harmonize-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface conflicts across OpenSpec changes to ensure coherent evolution.

Core Features & Use Cases

  • Index active and archived changes
  • Detect overlapping scopes across specs, domains, and endpoints
  • Distinguish intentional supersessions from accidental conflicts
  • Generate a structured harmony report for governance

Quick Start

Provide a change name as an argument to analyze a specific change, or leave empty to analyze all active changes, then run the harmonize tool

Frequently Asked Questions about openspec-harmonize-changes

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

FAQPage Schema
How do I detect overlapping scopes across OpenSpec changes?

Detect overlapping scopes by parsing change metadata from proposal.md and design.md to compare active and archived changes. This generates a structured harmony report that surfaces accidental overlaps across specs, domains, and endpoints for governance.

How do I distinguish intentional supersessions from accidental conflicts in spec change management?

Distinguish intentional supersessions from accidental conflicts by comparing pairs or specific named changes across OpenSpec footprints. The analysis verifies whether overlaps are deliberate governance decisions or unintended design collisions.

Can I analyze a specific named change instead of all active OpenSpec changes?

Analyze a specific named change by providing the change name as an argument to the harmonize tool. If left empty, the tool defaults to analyzing all active changes to ensure coherent evolution.

What is OpenSpec change harmonization for coherent architecture evolution?

OpenSpec change harmonization is the process of indexing active and archived changes to identify conflicts across specs. It ensures coherent evolution by generating a structured harmony report for governance tracking.

Do I need proposal.md and design.md files to generate a harmony report?

Generate a structured harmony report by parsing change metadata from proposal.md and design.md files along with footprints in openspec/changes. These files provide the required metadata to index changes and detect overlapping scopes.