orchestrate-my-tickets
Skill1 starsChanged 5 months agoNo licenceView on GitHub
Works a batch of tickets — a sprint, an epic, a status column, or a pasted key list — in parallel at every stage, by running `orchestrate-ticket` in one worktree-isolated sub-agent per ticket and keeping every gate in the main session. One state and readiness sweep across the whole set, a confirmation gate before anything is dispatched, then rounds - agents work until their first gate and report back, the main session dispatches the independent verifiers, puts every pending write and question on a localhost kanban board where the user approves on the card, makes each approved write, and resumes that agent - until every ticket waits on someone outside the run. Covers holding a dependent or file-overlapping ticket until the ticket it depends on has its PR open, running one promote for the whole batch, and collecting the final table from the board rather than from the agents. Use for "work all my sprint tickets", "run orchestrate-ticket on each of my tickets in sub-agents", or any batch of tickets at mixed stages that should move on together. To only turn ready tickets into PRs, with agents that open them themselves, use dispatch-ready-tickets. Skip for a single ticket — that is `orchestrate-ticket` inline.
In this repository19 other files it gives its agents.
- orchestrate-my-tickets/AGENTS.mdAGENTS.md
- orchestrate-my-tickets/CLAUDE.mdCLAUDE.md
- ai-review-and-fixSkill
- approve-addressed-prsSkill
- create-design-briefSkill
- create-html-presentationSkill
- fix-pr-commentsSkill
- fix-pr-conflictsSkill
- fix-review-commentsSkill
- get-dev-ticketsSkill
- get-staging-ticketsSkill
- grill-meSkill
- merge-conflict-resolverSkill
- orchestrate-ticketSkill
- pr-deskSkill
- pre-pr-review-and-fixSkill
- quick-commit-pushSkill
- review-prSkill
- verify-pr-review-repliesSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
6
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.