/usecase-dev-task-queue
Create and run an agent-ready development queue from issues/PRs with progress checkpoints.
$ npx -y skills add CoWork-OS/CoWork-OS --skill usecase-dev-task-queue --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/usecase-dev-task-queue
Context preview
The summary Claude sees to decide when to auto-load this skill.
Create and run an agent-ready development queue from issues/PRs with progress checkpoints.
SKILL.md
usecase-dev-task-queue.SKILL.mdname: usecase-dev-task-queue
description: "Create and run an agent-ready development queue from issues/PRs with progress checkpoints."
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
| Name | Type | Required | Description | |---|---|---|---| | repository | string | Yes | Repo slug or URL | | scope_filter | string | No | Optional scope (label, milestone, area, keyword) | | max_parallel_tasks | number | No | Maximum active tasks in parallel | | progress_channel | select | No | Where 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`.
Read more
name: usecase-dev-task-queue description: "Create and run an agent-ready development queue from issues/PRs with progress checkpoints."
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
| Name | Type | Required | Description | |---|---|---|---| | repository | string | Yes | Repo slug or URL | | scope_filter | string | No | Optional scope (label, milestone, area, keyword) | | max_parallel_tasks | number | No | Maximum active tasks in parallel | | progress_channel | select | No | Where 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`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill