doc-to-issues
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Turn a project's SPEC.md into small, independently-implementable issue files under issues/, so any agent can pick one up without re-deriving how the spec decomposes into work. Flags issues touching auth, secrets, or untrusted input as security-sensitive, used downstream by implement-issue and qc for extra scrutiny. Classifies each issue's owner — agent (fully agent-doable), user (hard blocker needing credentials/business decisions only the user can supply), or placeholder (soft preference like colors/copy, filled with a flagged default) — so implement-issue knows what it can pick up automatically. Keeps issues in sync on rerun as SPEC.md evolves — adds issues for new content, leaves in-progress/done issues alone except flagging done issues hit by a security change, marks stale issues instead of deleting, keeps FEATURES.md honest. Use when turning a spec into issues/tasks/tickets, or invoking /doc-to-issues. Requires an existing SPEC.md — if none, use interview first.
In this repository9 other files it gives its agents.
- documentationSkill
- implement-backlogSkill
- implement-issueSkill
- interviewSkill
- polishSkill
- qcSkill
- reportSkill
- review-issueSkill
- staging-qa-docSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 4 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.