Add an OpenSpec-Identifier to the prompts.
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
Find the workflow prompt files and compare their existing front matter and headings. Add a heading naming each prompt's skill, following the issue's examples. Check the prompts to confirm each has an identifiable skill name; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Description
The problem, in one or two sentences
I am using following instruction in the AGENTS.md:
Always use the OpenSpec skills for codebase changes, except for solving merge conflicts.
Useopenspec-proposeto plan a new change,openspec-update-changeto revise an existing plan, and
openspec-apply-changeto implement it. Follow their instructions; they provide
the required context and schema-specific workflow.
This works very well, but when I use the provided prompts in workflow automations, the agent still loads the skill.
Who this affects
Probably only people with similar instructions, who then use the prompt.
The change, however, would be minimal, and provide an improvement that makes the prompts identifiable.
What you tried
( I can change the prompts myself, but I think this would improve OpenSpec)
What you have in mind
Add a Heading to each prompt with the title of the skill.
e.g. (my favorite):
---
description: "Implement tasks from an OpenSpec change (Experimental)"
---
# openspec-apply-change
...
or
---
description: "Implement tasks from an OpenSpec change (Experimental)"
---
# Openspec Apply Change
...
This would make each prompt identifiable for an Agent. And I could add an exception "if an openspec prompt has been already provided" (or similar).
Remark: I helpful, I can provide the changes.
- 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 83/100
Fission-AI/OpenSpec#2157 · 2 comments ·
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
All issues in Fission-AI/OpenSpec
Similar issues
-
Add: Disco Mix SDOpencheck:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
level2 nsoc26
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
GauravKarakoti/SecureFlow#1488 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
deltachat/deltachat-desktop#6914 ·
Maintainers usually reply within 2 days
-
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