run-decision-queue
Skill0 starsChanged 46 days agoNo licenceView on GitHub
Run a ruling session whenever you hold more than one open point for the owner to rule on: plan open questions, audit findings, review findings, deferred items. Stage the points in a task list, raise one at a time with context, options, and one recommendation, and record each ruling in its durable home before you raise the next. Use it instead of sending the points as one list. Start it on your own initiative, without being asked, as soon as two or more points are pending, for example when several planning, audit, or review reports come back with open questions. Keep the queue moving while dispatched work runs in the background. The project's documents own where rulings are recorded.
In this repository8 other files it gives its agents.
- adopt-orchestrationSkill
- design-agent-workflowSkill
- execute-runbookSkill
- implement-ticketSkill
- open-pull-requestSkill
- orchestrate-implementationSkill
- orientationSkill
- resume-orchestrationSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
1
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.