Skip to content

[Change] Spec-Kit Change Proposal Bridge & Backlog Extension Sync #116

@djm81

Description

@djm81

Change Proposal: speckit-03-change-proposal-bridge

Change folder: openspec/changes/speckit-03-change-proposal-bridge/

Why

Users need to draft OpenSpec change proposals from spec-kit feature folders and synchronize backlog issues between spec-kit extensions and SpecFact. Currently no bridge exists to convert between spec-kit features and OpenSpec changes, and spec-kit backlog extensions (Jira, ADO, Linear) can create duplicate issues when SpecFact also syncs to the same tools.

What Changes

  • Bidirectional conversion: spec-kit feature → OpenSpec change proposal and vice versa
  • Backlog extension issue detection: detect issues created by spec-kit Jira/ADO/Linear/GitHub Projects extensions
  • Duplicate prevention: skip issue creation during SpecFact backlog sync when spec-kit already created them
  • New --mode change-proposal option on specfact sync bridge command
  • Profile-aware sync behavior (solo/team/enterprise)

Capabilities

  • New: speckit-change-proposal-bridge, speckit-backlog-extension-sync
  • Modified: backlog-sync

Blocked By

  • specfact-cli #453 (speckit-02-v04-adapter-alignment) — requires ToolCapabilities.extension_commands

Validation

  • openspec validate --strict passed
  • ✅ No breaking changes detected (all additive)
  • See CHANGE_VALIDATION.md in change folder

Metadata

Metadata

Assignees

Labels

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions