steer-queue
Skill0 starsChanged 37 days agoMITView on GitHub
Organize new steering instructions without losing current work.
In this repository8 other files it gives its agents.
- browser-qaSkill
- compact-checkpointSkill
- evidence-completionSkill
- jev-judgeSkill
- rule-rubricSkill
- safety-preflightSkill
- seo-auditSkill
- targeted-file-relevanceSkill
The file
Files
Apply a steer/queue pass for: $ARGUMENTS
- Summarize the current objective and current step.
- Classify the new instruction as
STEER NOW,QUEUE NEXT,REPLACE, orCONFLICT. - Preserve completed evidence and explicitly cancel obsolete steps.
- Order remaining work by dependency and risk, with a bounded next action.
- Surface any conflict that requires user choice.
This is a planning protocol only. It does not provide interrupt routing, background scheduling, or message delivery.
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.