agentleFS
enkr1enkr1/claude-code-skills/skills/dequeue/SKILL.md

dequeue

Skill1 starsChanged 23 days agoMITView on GitHub

Pop the top item off the handoff queue and do it. Use at the start of a fresh session to continue queued work, or when the user says "pop", "dequeue", "deq", "takeover", "接手", "pick up the queue", "what's queued", "continue where we left off", or "resume the handoff". Paired with the enqueue skill, which writes items into the queue.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the doc top to bottom, then follow its own contract:

    line 34
  2. Very specific:

    Thin Decisions or Why?: Read the discussion back off Source session:, never guess or re-ask: references/edge-cases.md.

    line 42
  3. Distinctive:

    When the work is on origin, or the user says it is done:

    line 48
  4. Distinctive:

    One pop per invocation: After acking, show what's next in the queue and stop.

    line 60

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dequeue

Take the top handoff off the queue, do its work, ack it when the work lands.

Pop means it leaves the queue now. hd.sh pop [slug] moves the doc into drafts/ at the pick, before you read a line of it, so no other session can take it and nothing has to earn its way out. Then DO its Next action. Why: under the old peek + ack, only a session that had verified 100% of the Done-when could pop, and on 2026-10-19 two sessions held shipped work for a phone check the owner never asked for ("so dumb").

Landed is done. Once the work is on origin, hd.sh ack <slug>. A check you could not run is one line in the report, never a reason to keep the doc and never a question to the user: no "say done", no "look at it on your phone", no "say deploy and I'll pop". Their look, their word and a promotion come after the ack, not before it.

Context size never justifies refusing, narrowing or deferring what the user asked for. It is a prompt to offer the close; their "do it" ends it.

The queue

~/.claude/handoffs/ is the queue, no index file. A pending item is p<N>-<yyyymmddhhmm>-<slug>.md at the top level, p0 (drop-everything) through p3 (backlog), sorted lexically: lower p first, oldest first within a priority. drafts/ holds docs nobody asked to queue and docs a session popped; done/ holds acked and expired ones and is never resumed from.

~/.claude/scripts/hd.sh list prints it: first line is the top, no output means empty, and empty means say so and stop.

Before you pop, reconcile (ack docs whose State names a pushed sha on origin) and triage (cap 20, no p3): references/triage.md.

Selecting

  • Bare → hd.sh pop: it takes the head. Announce it (item, priority, how many remain, siblings sharing its **Source session:**) so the user can redirect.
  • With a slug → hd.sh pop <slug>; a doc already in drafts/ prints its path, so resume it there. Report what you skipped at the END.
  • "list" / "what's queued" → the sorted queue, one line each (priority, age, slug, the doc's Next action first line). No pop, no work.
  • Ambiguous slug → show the matches, ask.

Resuming

Read the doc top to bottom, then follow its own contract:

  1. Run Preflight exactly as written. A check showing the work already landed means ack it now and say so.
  2. Follow any docs/feature-<name>.md pointer BEFORE Next action, reading its Decided and Open first. The feature doc holds the decisions and wins when the two disagree.
  3. Read Decisions, then start at Next action. A decision there can have superseded a gate the rest of the doc still assumes.
  4. Respect Authority. It says what you may do alone; a promotion (./deploy-web.sh) stays the user's word and never holds the ack.
  5. Reality diverging from State beyond what Preflight anticipated: report the divergence, propose the adjusted plan, get a nod.

Thin Decisions or Why? Read the discussion back off **Source session:**, never guess or re-ask: references/edge-cases.md.

The doc stays live while you work. Session state goes back into it (hd.sh <slug> state '<fact>' finds it in drafts/); a DECISION goes into the feature doc in the same commit as the code it governs, never only into the handoff.

Ack

When the work is on origin, or the user says it is done:

~/.claude/scripts/hd.sh ack <slug>

Every bullet under Open questions and Still open is disposed of first, marked in place as DONE, MOVED <slug | docs/feature-<name>.md | todo file> or DROPPED <reason>; a question whose built default shipped is DONE (default kept). With a docs/feature-*.md pointer, ack also needs a **Sweep:** line and refuses on any stale status line in docs/; its message says how to clear it.

Proof is the sha on origin, read this session (git merge-base --is-ancestor), plus the checks Done when names, run before the push. Unpushed work never acks. rm is never the ack, and done/ is the undo.

Report what landed (sha, which env you checked), one line on anything you could not check, and the remaining queue.

One pop per invocation. After acking, show what's next in the queue and stop; chaining items uninvited is scope grab.

Ending with the work not on origin yet: references/ending-unfinished.md.

Edge cases

references/edge-cases.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.