spec-to-issue
Skill1 starsChanged 2 months agoMITView on GitHub
Open a GitHub issue from a numbered spec file (docs/specs/0003-title.md), with the spec's summary, a checklist of its requirements, and a link back to the document. Use this whenever the user says "create an issue for spec 0003", "file a GitHub issue from this spec", "put this spec on the board", "open a ticket for that spec", or asks to track, assign, or hand off a spec as work. Also use when a spec has just been written and the user wants it queued up for someone to pick up.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- anyoneanderson/agent-skillstheir own version, first seen Oct 13, 2026
- jwrobes/skillstheir own version, first seen Oct 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- anyoneanderson/agent-skills★ 3same name
- jwrobes/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- software-engineerSkill
- implement-specSkill
- pm-feature-advisorSkill
- spec-writerSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Status: If it's already Implemented, the work is done — ask the user what they're after before filing an issue for it.
- Very specific: line 59
If the script exits reporting a possible duplicate, don't reach for --force reflexively.
- Distinctive: line 63
If the user hasn't said which labels or assignees they want, ask before creating rather than guessing — those choices route the work to …
- Distinctive: line 75
Don't close or edit existing issues as part of this.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Spec to Issue
Turn a spec into a trackable GitHub issue: title, summary, requirements checklist, and a link back to the spec.
Requires the gh CLI, authenticated (gh auth status), in a repo with a GitHub remote.
Read the spec first
Open the spec and check three things before doing anything:
- Status. If it's already
Implemented, the work is done — ask the user what they're after before filing an issue for it. They may be looking at the wrong spec number. - An issue may already exist. The script searches open and closed issues for the spec number and refuses to create a duplicate, but a differently-worded title can slip past it. If you spot a match it missed, show the user and let them decide.
- Requirements. These become the issue's checklist, so they're the part worth reading closely.
Write the issue body
Let the script generate the default body when the spec is straightforward. Write your own when the spec needs framing the document doesn't provide — a dependency on other work, an explanation of why now, a scope note for whoever picks it up.
A good body is short, because the spec is the real document and duplicating it into the issue guarantees the two drift apart:
Implements [0003 — Rate limit the public API](docs/specs/0003-rate-limit-public-api.md).
Public endpoints currently have no request ceiling, so a single misbehaving
client can degrade the API for everyone.
## Requirements
- [ ] 1. Per-key request counting in a sliding window
- [ ] 2. 429 with `Retry-After` when the limit is exceeded
- [ ] 3. Admin tokens get a raised ceiling, not a bypass
Full detail, including the non-goals, is in the spec.Link to the spec by repository-relative path so GitHub resolves it against the default branch. If the spec isn't merged to the default branch yet, say so in the body — otherwise the link 404s and the reader assumes the issue is stale.
Create it
scripts/create_spec_issue.sh docs/specs/0003-rate-limit-public-api.mdOptions:
--body-file <path>— use your own body instead of the generated one--label <name>— repeatable; labels that don't exist in the repo are skipped with a warning rather than failing the call--assignee <user>— repeatable;@meworks--milestone <name>--dry-run— print the title, labels, and body without creating anything--force— create even though the duplicate search found something--repo <owner/name>— target a different repo
If the script exits reporting a possible duplicate, don't reach for --force reflexively. Show the user what it found. Re-filing work that already has an issue splits the discussion across two threads, and the older issue usually has context the new one won't.
Use --dry-run first when you generated the body yourself, or when the spec's requirements are long enough that the checklist might have parsed badly. An issue is visible to everyone watching the repo the moment it's created, and editing a mistake leaves the original in the notification emails. A dry run costs nothing.
If the user hasn't said which labels or assignees they want, ask before creating rather than guessing — those choices route the work to people, and a wrong assignee is a notification someone has to untangle.
After creating
Report the issue URL and number.
Consider mentioning the issue number in the spec, or the spec path in later commits, so the two stay findable from each other. Don't edit the spec's frontmatter to add an issue field unless the user asks — the spec format is defined elsewhere, and quietly adding fields to it makes specs inconsistent across the repo.
What not to do
Don't create an issue per requirement. The spec is the unit of work; a checklist inside one issue keeps the discussion in one place, and seven issues that all link back to the same document is noise on the board. If the user genuinely wants the requirements split across issues, do it — but say once that the spec-sized issue is usually easier to track.
Don't close or edit existing issues as part of this. Creating is the whole job.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

