agentleFS
SharqiewiczSharqiewicz/skills/make-ticket/SKILL.md

make-ticket

Skill1 starsChanged 42 days agoNo licenceView on GitHub

Turn ideas, conversations, and plans into structured, testable work on the issue tracker. Three flows: (A) draft a single GitHub Issue in User Story format with Definition of Ready/Done; (B) synthesize the current conversation into a PRD; (C) break a plan or PRD into independently-grabbable tracer-bullet issues. Triggers on: github issue, create issue, new issue, user story, feature request, bug report, task, backlog item, DoR, DoD, acceptance criteria, write a PRD, turn this into a PRD, break this into issues, slice into tickets, vertical slices, tracer bullets.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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.

Reviews can't be read right now.

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.