OpenParable
Skip to content
← Back to skills

Usecase Dev Task Queue

Productivity
usecase-dev-task-queue

Usecase Dev Task Queue is an Agent Skill for productivity published in the CoWork-OS/CoWork-OS repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CoWork-OS/CoWork-OS/blob/HEAD/resources/skills/usecase-dev-task-queue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/usecase-dev-task-queue, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.