Main spec is never created for the first change in a greenfield project

[sebastian-zarzycki-apzumi]

I've initialized a new OpenSpec project through CLI. I've configured it to use commands for OpenCode. Via OpenCode, using standard build agent, I've created a new change, applied it and then archived it. It just went into /changes/archive and not to /specs where I expected it to land.

Is there something wrong in this assumption? Am I to arbitrary create some initial specs under /specs, even if I'm starting a project from scratch? Should it have a specific format or be an empty file? I would expect archive to do just that.

[sam74]

I am experiencing the same issue with openspec version 1.3.1. and 1.4.1 with codex.

How I resolved the problem:

The first application of $openspec-archive-change doesn't generate specs because it doesn't find any already defined capabilities.

To get the first specs in openspec/specs/<...>,

I run $openspec-sync-specs.

Subsequent commands from $openspec-archive-change will synchronize the specs as expected.

[sebastian-zarzycki-apzumi]

Interesting, thanks. So you're force-running sync before first archive, right? Isn't sync supposed to be executing automatically during archive anyway? From the docs:

Optional command. Merge delta specs from a change into main specs. Archive will prompt to sync if needed, so you typically don't need to run this manually.. Perhaps the prompting of "when needed" is ambiguous and should improve, i.e. it's also needed, when it's not there yet.

[sam74]

Yes, I agree with you "sync supposed to be executing automatically during archive ", but it is not the case. I hope we will get a clarification as it is related to the core workflow of openspec.