[Bug] /opsx:update guardrails contradict the new glob-artifact file creation
Maintainers usually reply within 2 days
A pull request for this has already been merged.
- #2083 by @clay-good — merged
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 87/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Read .claude/commands/opsx/update.md and .claude/skills/openspec-update-change/SKILL.md, focusing on their Guardrails sections and step 4. Update the first guardrail in both files to include the confirmed concrete path exception for a partly populated glob artifact. Done when the guardrails no longer contradict step 4.
Written by the indexing model from the issue text.
Description
Summary
The guardrails of /opsx:update contradict the new behavior for filling a missing file under a partly written glob artifact. Step 4 now allows creating a confirmed concrete path, but the first guardrail still says to edit only files already listed in existingOutputPaths, and a new file is by definition not in that list. An agent that applies the stricter blanket rule refuses the new-file operation, so the flow added for partly written glob artifacts can fail to fill the missing spec.
Version
@fission-ai/openspec 1.14.1, Claude Code delivery (skills + commands), spec-driven schema.
Where
.claude/commands/opsx/update.md, Guardrails:
- "Edit only the concrete files in
existingOutputPaths; never write to a globresolvedOutputPath." - followed two bullets later by "... The only new-file scope is a confirmed concrete path under a glob artifact whose
existingOutputPathsis non-empty."
The same wording is in .claude/skills/openspec-update-change/SKILL.md.
Suggested fix
State the exception on the first bullet, where an agent applying the stricter rule will read it: for example "Edit only the concrete files in existingOutputPaths, plus the one confirmed concrete path allowed under a partly populated glob artifact (step 4); never write to a glob resolvedOutputPath." Apply it to both the command and the skill.
- Dominant language
- TypeScript
- Stars
- 71.6k
- Forks
- 4.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 82
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
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Fission-AI/OpenSpec#2099 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Fission-AI/OpenSpec#2098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Fission-AI/OpenSpec#1966 · 1 comment ·
Maintainers usually reply within 2 days
-
feat(schemas): open each proposal with a short review focusPossibly taken @GaoSSR claimed this 27 days ago. Opendesign-review
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Fission-AI/OpenSpec#1908 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Fission-AI/OpenSpec#2088 ·
Maintainers usually reply within 2 days
All issues in Fission-AI/OpenSpec
Similar issues
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 72/100
sujithputta02/Esapay#13 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ehmpathy/rhachet-roles-bhuild#468 ·
Maintainers usually reply within 1 day
-
Share dialog: the address book's contact count reads "1 contacts" (no singular form in any language)Possibly taken @chibenwa claimed this today. Openai-driven-qa bug claude Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
linagora/twake-contacts-frontend#271 · 1 comment ·
Maintainers usually reply within 1 day
-
factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Koenkk/zigbee2mqtt#33402 ·
Maintainers usually reply within 1 day