docs(community): add openspec-steward
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Open docs/community.md and find the "Projects and resources" section. Add the provided bullet point for openspec-steward exactly as described. Done when the entry is present and correctly formatted; no tests are required.
Written by the indexing model from the issue text.
Description
Where
docs/community.md, under "Projects and resources"
What is wrong or missing
openspec-steward is a Claude Code plugin for repositories that use OpenSpec. It has two parts. The first is a change flow, run by commands such as /start-change and /archive-on-green, where nothing waits for a person except the merge. The second is a CI checker that catches what openspec validate cannot: a MODIFIED delta that silently drops a scenario, and a requirement whose list of routes no longer matches the code. It is MIT-licensed and free, needs no account, and sends nothing to any server.
What it should say instead
- openspec-steward: Claude Code plugin with a change flow gated only at merge, and a CI checker that fails when a
MODIFIEDdelta silently drops a scenario or a declared inventory drifts from the code.
- Dominant language
- TypeScript
- Stars
- 73.6k
- Forks
- 5k
- Avg merge
- 4d 43m
- Merged PRs (30d)
- 64
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
-
documentation needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Fission-AI/OpenSpec#2187 ·
Maintainers usually reply within 2 days
-
archive and sync skills merge every `specs/**/*.md` as a delta spec, including files `validate` rejectsPossibly taken @clay-good claimed this 4 days 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 4 days 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 4 days 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 83/100
Fission-AI/OpenSpec#2157 · 2 comments ·
Maintainers usually reply within 2 days
All issues in Fission-AI/OpenSpec
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LucasSantana-Dev/Lucky#2951 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2567 ·
Maintainers usually reply within 9 days
-
refactor(react-pi): classify base64 images with core's parseBase64Possibly taken @jimmyallinai claimed this today. Openmaintenance
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
assistant-ui/assistant-ui#10293 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
brijeshb42/monaco-vim#175 ·