`openspec init` won't create default `spec-driven` schema

[JimMoen]

Version

$ openspec -V
1.1.1

---

as the document mention, run openspec init, and then:

$ openspec new change test
✖ Failed to create change 'test'

✖ Error: Unknown schema 'spec-driven'. Available:

⬆️ NO output after the "Available:". And then I ran:

$ openspec schema init spec-driven
Note: Schema commands are experimental and may change.
✔ Schema description: Custom workflow schema for spec-driven
✔ Select artifacts to include: proposal, specs, design, tasks
✔ Set as project default schema? No
✔ Created schema 'spec-driven'

Schema created at: /home/xxx

Artifacts: proposal, specs, design, tasks

Next steps:
  1. Edit /home/xxx
  2. Modify templates in the schema directory
  3. Use with: openspec new --schema spec-driven

Then:

$ openspec new change test
✔ Created change 'test' at openspec/changes/test/ (schema: spec-driven)

---

Perhaps after openspec init, it's necessary to automatically create the default schema spec-driven, or prompt the user to execute openspec schema init

And The documentation docs/getting-started.md does not mention the need for openspec schema init.

[TabishB]

@JimMoen Can you tell me what platform you're on? i.e Windows, Linux etc

The behaviour is that it should default to using whatever's mentioned in the package

[kenOfYugen]

@TabishB I can confirm the same exact behavior on the aur/openspec 1.1.1-1 on Linux 6.18.7-arch1-1
Unless the openspec schema init spec-driven is executed after openspec init, RooCode can't make proper use of openspec. So my understanding is that it should be either documented as @JimMoen suggested, or perhaps it would be better be the final step in the openspec init interactive walkthrough, e.g. Set spec-driven as the project default schema? Y/n

[JimMoen]

I use the aur/openspec (1.1.1-1) on ArchLinux

[clay-good]

Fixed in current releases. The spec-driven schema now ships bundled in the npm package (package.json files includes schemas/) and resolves as a built-in — openspec schema which spec-driven reports Source: package. No openspec schema init step is needed after openspec init. This was a packaging gap in v1.1.1. Closing as fixed — please upgrade.