version-orchestration

Compare installed and project plugin versions and output a mismatch report.

39|3|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill version-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-orchestration
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/core/skills/orchestrators/version-orchestration
Command: npx skills add https://github.com/LiorCohen/sdd --skill version-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly verify that the installed plugin version matches the project's expected version, preventing drift after upgrades and ensuring compatibility.

Core Features & Use Cases

  • Compare installed and project plugin versions and highlight mismatches.
  • Handle legacy project version keys and report historical context for versions.
  • Use in project follow-ups to decide on plugin upgrades or reconciliations.

Quick Start

Invoke the version orchestration to display the installed and project plugin versions and report any mismatch.

Frequently Asked Questions about version-orchestration

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

FAQPage Schema
How do I check if my installed plugin version matches the project settings?

To check plugin version mismatches, compare the installed version from plugin.json against the project version specified in sdd-settings.yaml. This verification prevents drift after upgrades and ensures environment compatibility.

What happens when project plugin versions differ from installed versions?

When project plugin versions differ from installed versions, a version report highlights the mismatches. This helps you decide whether to perform plugin upgrades or reconcile project settings to restore compatibility.

How do I handle legacy project version keys during a semver comparison?

Legacy project version keys are automatically supported during semver comparison. The tool reads historical context from these keys and includes them in the version report alongside current sdd-settings.yaml values.

Can I detect plugin version drift in SDD project directories after an upgrade?

Yes, you can detect plugin version drift in SDD project directories by running a comparison of installed and project versions. It reads installed data from plugin.json and project data from sdd-settings.yaml to report discrepancies.

Why does my project specify a different plugin version than what is installed?

A project may specify a different plugin version than installed due to recent upgrades or environment drift. Comparing sdd-settings.yaml against plugin.json identifies these mismatches and provides historical context for reconciliation.

Does the version comparison work with both modern settings files and legacy keys?

Yes, the version comparison works with both modern sdd-settings.yaml files and legacy project version keys. It reads project versions from either source and performs semver checks against the installed plugin.json version.