mcpField
U
usecase-dev-task-queue

usecase-dev-task-queue

github.com/cowork-osAgent workflows51452 installsUpdated today
Repository

About usecase-dev-task-queue

A skill that turns issues or pull requests into a prioritized queue for agent-led development, with progress checkpoints and approval gates. It is for software teams coordinating execution while preventing unapproved merges or deployments.

Key features

  1. 01Build a prioritized development queue
  2. 02Filter by label, milestone, area, or keyword
  3. 03Track execution progress
  4. 04Set approval checkpoints
  5. 05Gate merges and deployments

Use cases

  1. 01Queue repository issues for agent execution
  2. 02Track progress across software tasks
  3. 03Require approval before merge or deployment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cowork-os/cowork-os --skill usecase-dev-task-queue

After installing, type/usecase-dev-task-queuein Claude Code to confirm it loaded.

Details

From the project README

Dev Task Queue

Purpose

Create and run an agent-ready development queue from issues/PRs with progress checkpoints.

Routing

  • Use when: Use when the user asks to queue software tasks for agent execution with progress updates and safe merge/deploy gating.
  • Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead. Use /batch for broad cross-domain migration workflows.
  • Outputs: Outcome from Dev Task Queue: prioritized queue, execution status, and explicit approval checkpoints.
  • Success criteria: Builds a practical task queue with visible progress and no unsafe autonomous merge/deploy actions.

Trigger Examples

Positive
  • Use the usecase-dev-task-queue skill for this request.
  • Help me with dev task queue.
  • Use when the user asks to queue software tasks for agent execution with progress updates and safe merge/deploy gating.
  • Dev Task Queue: provide an actionable result.
Negative
  • Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead. Use /batch for broad cross-domain migration workflows.
  • Do not use usecase-dev-task-queue for unrelated requests.
  • This request is outside dev task queue scope.
  • This is conceptual discussion only; no tool workflow is needed.

Parameters

NameTypeRequiredDescription
repositorystringYesRepo slug or URL
scope_filterstringNoOptional scope (label, milestone, area, keyword)
max_parallel_tasksnumberNoMaximum active tasks in parallel
progress_channelselectNoWhere progress updates should be formatted for

Runtime Prompt

  • Current runtime prompt length: 1159 characters.
  • Runtime prompt is defined directly in ../usecase-dev-task-queue.json.

Comments

Markdown supported