mirror of https://github.com/Fission-AI/OpenSpec.git synced 2026-09-14 20:16:53 +08:00

Files

T

Tabish Bidiwale 9228ee798c feat: add /opsx:sync command for syncing delta specs to main specs

Add a new agent-driven skill that syncs delta specs from a change to main specs
without requiring archiving. This enables:

- Updating main specs during active development
- Intelligent merging (partial updates, adding scenarios)
- Idempotent operation (safe to run multiple times)

Implementation:
- Extract shared specs-apply logic from archive.ts to specs-apply.ts
- Add getSyncSpecsSkillTemplate and getOpsxSyncCommandTemplate
- Register /opsx:sync in artifact-experimental-setup
- Add specs-sync-skill main spec

2026-01-06 16:16:07 -08:00

2.9 KiB

Raw Permalink Blame History

specs-sync-skill Specification

Purpose

Defines the agent skill for syncing delta specs from changes to main specs.

Requirements

Requirement: Specs Sync Skill

The system SHALL provide an /opsx:sync skill that syncs delta specs from a change to the main specs.

Scenario: Sync delta specs to main specs

WHEN agent executes /opsx:sync with a change name
THEN the agent reads delta specs from openspec/changes/<name>/specs/
AND reads corresponding main specs from openspec/specs/
AND reconciles main specs to match what the deltas describe

Scenario: Idempotent operation

WHEN agent executes /opsx:sync multiple times on the same change
THEN the result is the same as running it once
AND no duplicate requirements are created

Scenario: Change selection prompt

WHEN agent executes /opsx:sync without specifying a change
THEN the agent prompts user to select from available changes
AND shows changes that have delta specs

Requirement: Delta Reconciliation Logic

The agent SHALL reconcile main specs with delta specs using the delta operation headers.

Scenario: ADDED requirements

WHEN delta contains ## ADDED Requirements with a requirement
AND the requirement does not exist in main spec
THEN add the requirement to main spec

Scenario: ADDED requirement already exists

WHEN delta contains ## ADDED Requirements with a requirement
AND a requirement with the same name already exists in main spec
THEN update the existing requirement to match the delta version

Scenario: MODIFIED requirements

WHEN delta contains ## MODIFIED Requirements with a requirement
AND the requirement exists in main spec
THEN replace the requirement in main spec with the delta version

Scenario: REMOVED requirements

WHEN delta contains ## REMOVED Requirements with a requirement name
AND the requirement exists in main spec
THEN remove the requirement from main spec

Scenario: RENAMED requirements

WHEN delta contains ## RENAMED Requirements with FROM:/TO: format
AND the FROM requirement exists in main spec
THEN rename the requirement to the TO name

Scenario: New capability spec

WHEN delta spec exists for a capability not in main specs
THEN create new main spec file at openspec/specs/<capability>/spec.md

Requirement: Skill Output

The skill SHALL provide clear feedback on what was applied.

Scenario: Show applied changes

WHEN reconciliation completes successfully
THEN display summary of changes per capability:
- Number of requirements added
- Number of requirements modified
- Number of requirements removed
- Number of requirements renamed

Scenario: No changes needed

WHEN main specs already match delta specs
THEN display "Specs already in sync - no changes needed"

2.9 KiB Raw Permalink Blame History