Community schema: spec-driven-ids
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 83/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Edit the Community Schemas table in docs/customization.md, using the proposed row and the linked repository for details. Read the existing table and its contribution note first. Done when the spec-driven-ids row accurately lists its maintainer, repository, and description.
Written by the indexing model from the issue text.
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. |
- Dominant language
- TypeScript
- Stars
- 73k
- Forks
- 5k
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 69
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Fission-AI/OpenSpec
-
archive and sync skills merge every `specs/**/*.md` as a delta spec, including files `validate` rejectsPossibly taken @clay-good claimed this 1 day ago. Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Fission-AI/OpenSpec#2173 ·
Maintainers usually reply within 2 days
-
openspec-apply-change skill: when blocked, may select a ready artifact unrelated to missingArtifactsPossibly taken @clay-good claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Fission-AI/OpenSpec#2165 ·
Maintainers usually reply within 2 days
-
openspec-archive-change skill: ignores delta specs when artifact ID is not "specs"Possibly taken @clay-good claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Fission-AI/OpenSpec#2163 · 1 reaction ·
Maintainers usually reply within 2 days
-
documentation needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Fission-AI/OpenSpec#2143 ·
Maintainers usually reply within 2 days
-
enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Fission-AI/OpenSpec#2105 ·
Maintainers usually reply within 2 days
All issues in Fission-AI/OpenSpec
Similar issues
-
area:cli bug P4
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug from-studio
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esengine/DeepSeek-Reasonix#14868 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
loopbackio/loopback-next#11878 ·
Maintainers usually reply within 2 days
-
bug 🐛
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
comunica/comunica#1925 · 1 comment ·
Maintainers usually reply within 1 day