Repository navigation
Community schema: spec-driven-ids #2157
Description
Where
https://github.com/Fission-AI/OpenSpec/blob/main/docs/customization.md, "Community Schemas" section
What is wrong or missing
The Community Schemas table has no row for spec-driven-ids, a community schema built on spec-driven. The note under the table says to open an issue with a repository link and a one line description, so here it is.
Repository: https://github.com/sonqh/spec-ctx/tree/main/schemas/spec-driven-ids
Context: #1967 (stable identifiers for requirements and scenarios).
What it should say instead
| Schema | Maintainer | Repository | Description |
|---|---|---|---|
spec-driven-ids |
@sonqh | sonqh/spec-ctx | spec-driven with a stable ID on every requirement, scenario, decision, and task. specctx allocates the IDs, bundles the spec of one task for an agent, and ticks a task only after its Verify command passes. Adopts an existing project in one run. |
Activity
docs: triage upstream issues Fission-AI#2155-Fission-AI#2157 and adva…
docs(openspec): consolidate stable IDs for requirements, scenarios an…
clay-good commentedon Oct 29, 2026
Thanks, @sonqh. Your
spec-driven-idsschema shaped #2167. #1979 makes validate and archive match on an ID at the start of a heading, written in square brackets ([REQ-UA-004]). The brackets keep words likeSHA-256from being read as IDs. Bare IDs like yours stay plain names, so nothing changes for spec-ctx until brackets are added. All 173 archived deltas in spec-ctx rebuild byte-identical with the change.sonqh commentedon Oct 30, 2026
Thanks, @clay-good. spec-ctx 0.3.0 now reads and writes the bracketed form from #1979. I left the details and some data for Decision 3 on the PR: #1979 (comment)