Feature Request: Target Main Specs on Sync and Archive

[caleb-reyes-op]

Feature Request: Target Main Specs on Sync and Archive

TL;DR

Allow /opsx:sync and /opsx:archive to target specific main specs, enabling changes to evolve a single main spec over time rather than creating conflicting spec files. OR, remove the main spec entirely -- the code **is** the most accurate state of things now.

Core Problem

A main spec should represent the current state of a feature, not a point in time. In brownfield development, features evolve over time through multiple changes. Currently, if multiple changes target the same main spec, they create separate spec files that could contradict each other.

Example

openspec/specs/ui/spec.md (main spec - current state)

openspec/changes/add-header/
  specs/ui/spec.md (delta spec - wants to update main spec)

openspec/changes/add-footer/
  specs/ui/spec.md (delta spec - wants to update same main spec)

If both changes create separate main specs, we end up with contradictory specifications.

Current Behavior

• /opsx:sync and /opsx:archive don't allow targeting specific main specs
• Changes can't easily evolve a single main spec over time
• Risk of creating contradictory spec files

Proposed Solution

Allow /opsx:sync and /opsx:archive to target specific main specs:

/opsx:sync --spec ui
/opsx:archive --spec ui

This enables:

1. Multiple changes to evolve the same main spec
2. Sequential archiving of related changes
3. Single source of truth for feature state

Benefits

• Single source of truth: One main spec per feature
• Evolvable: Specs can be updated over time
• No contradictions: Changes build on each other sequentially
• Brownfield friendly: Supports ongoing feature development

[nikhilmaddirala]

Currently, if multiple changes target the same main spec, they create separate spec files that could contradict each other.

When you merge each change, the change spec gets synced back to the main spec via the delta sync process. Doesn't that solve the problem? (At least that's how I think it's supposed to work)

[tanght1994]

I am a beginner, and my understanding is as follows:
The real problem is that there shouldn't be multiple changes affecting the same main spec simultaneously.
If they affect the same main spec, it means these changes are mutually affecting each other.
When running opsx:new change1, you don't know what changes change2 will make.
When running opsx:new change2, you don't know what changes change1 will make.
There's no need to wait until the archive stage, the mutual interference will occur during the process of advancing the changes.
I wonder if my understanding is correct, please correct me.

[clay-good]

Thanks for raising this, @caleb-reyes-op 🙏

This is about Add --spec targeting to sync/archive so changes evolve one main spec over time — OR remove main specs entirely. — an open-ended feature/design idea rather than a discrete, PR-actionable bug or task. To honor it properly we've moved it to Discussions, where it can keep evolving with community input and you can re-engage anytime:

👉 #1570

The original issue (and any comments) stays here for the record, so nothing is lost — please continue the conversation in the discussion above. Closing the issue in favor of that thread.