requeue
Reviews and reorders the queue an engineering loop or team works from — backlog, roadmap, todo, milestones — so the next work picked up is the right work. Pulls every open item with the attributes that decide order (acceptance stated or not, blocked, human-only, duplicated, contradicted between files, stale), ranks them against the project's intent by unblocking power, purpose, readiness, decay and cost, splits them into lanes (the loop can finish it · needs a bounded subloop · needs a gauntlet of approaches · needs a human), rewrites the top vague items into tasks with an object, a test and a bound, and proposes the new order without touching the repo. Use when someone asks what to work on next, wants the backlog or roadmap reprioritised, re-ranked, triaged or cleaned up, says the priorities are wrong or the roadmap is stale, asks which items the autonomous loop should be fed, or arrives from loop-economist because the loop's problem is its input rather than its actor.
- License 许可
- MIT
- 最近更新
- 2026-09-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- requeue
- description
- Reviews and reorders the queue an engineering loop or team works from — backlog, roadmap, todo, milestones — so the next work picked up is the right work. Pulls every open item with the attributes that decide order (acceptance stated or not, blocked, human-only, duplicated, contradicted between files, stale), ranks them against the project's intent by unblocking power, purpose, readiness, decay and cost, splits them into lanes (the loop can finish it · needs a bounded subloop · needs a gauntlet of approaches · needs a human), rewrites the top vague items into tasks with an object, a test and a bound, and proposes the new order without touching the repo. Use when someone asks what to work on next, wants the backlog or roadmap reprioritised, re-ranked, triaged or cleaned up, says the priorities are wrong or the roadmap is stale, asks which items the autonomous loop should be fed, or arrives from loop-economist because the loop's problem is its input rather than its actor.
02 资源文件 11
- 参考文档evals/evals.json2.3 KB
- 参考文档evals/gauntlet/BAR.md4.2 KB
- 参考文档evals/gauntlet/ROUNDS.md641 B
- 参考文档fixtures/mixed-queue/docs/BACKLOG.md415 B
- 参考文档fixtures/mixed-queue/docs/ROADMAP.md108 B
- 参考文档fixtures/mixed-queue/expect.json335 B
- 参考文档fixtures/mixed-queue/README.md52 B
- 参考文档references/ranking.md3.0 KB
- 参考文档references/report-template.md1.8 KB
- 参考文档references/sharpening.md2.1 KB
- 脚本scripts/queue.mjs10.1 KB
03 SKILL.md 正文
Requeue
A loop is only as good as what it is fed. Most loops that look broken are being handed items that were never tasks: no acceptance test, a decision buried inside, or the same item twice in two files with opposite statuses. No model fixes that. Requeue fixes the input.
flowchart LR
A["queue.mjs<br/>items + attributes · read-only"] --> B["hygiene<br/>duplicate · contradiction · ghost · stale"]
B --> C["rank<br/>unblocks › intent › readiness › decay › cost"]
C --> D["lanes<br/>loop · subloop · gauntlet · human"]
D --> E["sharpen the top<br/>object · test · bound"]
E --> F["proposal<br/>order · reasons · asks"]
F -. only when asked .-> G["write the queue file"]
The guard-rail
- Propose; do not rewrite. The repo is untouched unless the person names the file and asks. Reordering someone's roadmap unasked is the one thing this skill must never do.
- Rank against a written purpose. If no intent document exists, say so in the first line and rank on unblocking and readiness only — and say that the ranking is unanchored.
- Read bounded. Queue files fully; everything else by header.
- No subagents. One context, one pass.
- Leave a receipt: files read, items considered, repo untouched.
Workflow
1. Collect
node <skill-dir>/scripts/queue.mjs <repo-path> > <scratchpad>/queue.json
Every open item with file:line, section, whether it states an acceptance test, whether it is worded only as judgement, blocked markers, human-only markers, first-seen date, plus duplicates, contradictions between files, and the intent documents. Read all of it.
No queue file → say so in three lines and stop. There is nothing to reprioritise, and inventing a backlog is not the ask.
2. Hygiene first
references/ranking.md, hygiene section. Duplicates, contradictions,
ghosts, stale items. Resolve before ranking: ranking a list that
contains the same item twice produces two ranks for one piece of work.
For a contradiction, decide which is true from the repo — the commit, the code, the test — not from whichever file was edited last.
3. Rank
Five factors in strict precedence: unblocks › intent › readiness › decay › cost. One line of reason per ranked item, naming the deciding factor, and naming the loser when two factors disagreed. An item that traces to no sentence of intent is a deletion candidate, not a low rank.
4. Split the lanes
- loop — the loop can finish it unattended.
- loop, subloop — the approach is uncertain: budget try · verify · adjust rounds with a round cap.
- loop, gauntlet — more than one plausible approach and a costly wrong choice: the bar gets written before the attempts run.
- human — a credential, an account, a decision, a signature. It leaves the loop's queue and becomes a gate item with the exact ask.
- blocked — the blocker is named; if it is not, naming it is the item.
Mixing human-only items into the loop's lane is the most common cause of a loop that stalls while looking busy.
5. Sharpen the top
references/sharpening.md. Rewrite the top vague items — enough for the
next few ticks, not the whole list — into object · test · bound. Where no
test can be written, choose honestly between a question for a person, a
bounded spike, and deletion. Never pass an untestable item to the loop.
6. Write the proposal
references/report-template.md, exactly: ≤ 50 words, queue health, the
proposed order with reasons and lanes, what leaves the loop's queue, the
sharpened rewrites, hygiene rows, do-next (≤ 5), footer receipt. Then a
terminal summary of ≤ 8 lines.
7. Apply — only when asked
Write the accepted order into the file the loop actually reads, one commit, diff shown first. Keep the items' wording as sharpened, keep the file's existing format, and never delete an item in the same commit as a reorder — deletions are their own decision and their own diff.
Judgement calls
Unblocking beats value. A small thing three items wait on ships more work this week than the biggest item on the list.
Readiness is a cap, not a factor. An unready item cannot sit at rank 1: sharpen it, then rank it. Feeding it up the queue anyway is how a loop burns a run discovering the item was a wish.
Old is not the same as dead. Say the age; let the reader decide. Propose deletion only when nothing waits on it and it traces to no intent.
The queue the loop reads is the real one. When two files disagree, the file the driver loads wins, and the other becomes a pointer.
Don't rank what a person must do. Human items get a lane and an exact ask, not a position in a queue nobody is working.
Say when the order barely changes. "The current order is right; two items need sharpening" is a good outcome and a cheap one.
Files
scripts/queue.mjs— item + attribute collector;--self-test.references/ranking.md— the five factors, lanes, hygiene classes.references/sharpening.md— object · test · bound, and the three honest outcomes when no test can be written.references/report-template.md— the proposal, exactly.evals/— the prompts, andgauntlet/BAR.md, the bar this skill's proposals are graded against by a blind critic.
Related
loop-economist measures what the runs cost and hands off here when the
binding constraint is the input. loop-doctor reviews the loop's design.
04 同仓库更多 Skills
loop
one tick
wake-weight
暂无简介
solo-flow
Prescribes and audits a trunk-based git workflow for a repository with exactly one writer — a single autonomous agent or loop, with no other humans committing. One branch (main), local-only short-lived work branches, CI as the sole independent check (no PRs, nothing to review socially), and releases as tags cut directly off main rather than a develop/release branch dance. Use whenever someone is setting up or reviewing git/branching/release conventions for an agent-driven or loop-driven repo, asks whether to use GitFlow/GitHub Flow/GitLab Flow/trunk-based development, wants AGENTS.md or CLAUDE.md git rules written, is deciding whether a develop branch or long-lived feature branches earn their keep, or reports branch drift, a forgotten back-merge, or an autonomous loop that got confused about which branch it was on. Also use to sanity-check an existing branching setup that looks like GitFlow but has no other human collaborators to justify it, and when deciding how the agent should isolate each unit of work (git worktrees, a primary checkout that never leaves main, running items in parallel).
sharpen-intent
暂无简介
progress-dashboard
Publishes a one-page stakeholder progress dashboard for any git project — where it stands, what's waiting on people, whether it's stalled — from whatever records the project keeps (ADRs, decision notes, design graphs, roadmaps, gates, backlogs, changelogs, PRs). Use whenever someone asks how a project is going, wants a status update or progress report, asks "where are we", "what's blocked", "what's waiting on me/us", "what's left", or wants an existing dashboard refreshed.
loop-economist
Reviews what an engineering loop's actual runs cost and produced — reading Claude Code session transcripts and git history rather than the loop's documents. Reports tokens per shipped change, cache and subagent spend, rework and thrash, how often a human had to intervene, and whether the right agent, model or persona did each kind of work; scores six dimensions (effectiveness, efficiency, budget, plan quality, agent fit, convergence) into a verdict, and prescribes what closes each finding — a verifier seam, routing the searching out, a bounded subloop or a gauntlet for items one run cannot converge on, or handing the queue to requeue when the input rather than the actor is the problem. Use when someone asks how efficient or effective their loop or agents are, what the loop is costing in tokens or budget, whether it is worth running, why it keeps redoing the same work, whether it is using the right model or agents, how to orchestrate multiple agents or personas across the work, or wants their multi-agent build loop analysed, scored or made cheaper.