queue-add

Topics in the source

• queue-add
• When to load
• How to use
• Write a real gate
• --requires gates; --tag only labels
• Gotchas

Creates a task as a file — arsenal/tasks/ .md — carrying its title, priority, dependencies and acceptance gate, then prints the issue handle to open for it. The file is the task; the issue is the handle agents claim. CANARY: queue-add-loaded-2026-06-13-fb78d23e-c3d4e5f6a7b8c9d0 The user wants to add a task, ticket or work item to the queue ("queue this up", "enqueue", /queue-add). Seeding the queue from a list of tasks before starting workers. It prints the new id on stdout and, on stderr, the issue to open. Create that issue with the arsenal:task label and a visible arsenal-task: line in the body: the marker links issue to task, and the label makes it claimable work. --label is the board's short name (five words at most); it defaults to the first five words of the title. Use the printed id as a --deps argument for dependent tasks. The generated file carries a placeholder gate that fails until replaced. Replace it before the task is claimed: Only a fenced block is executed; prose and inline commands run nothing, so they pass everything. Load ${CLAUDESKILLDIR}/references/payload-template.md when writing the task body beyond the gate: test names to write failing first, and one refere

This is an excerpt. Refer to the complete source and its current requirements.