← ClaudeAtlas

opsx-exttask-queuelisted

Use when the user wants new code written or new behavior added that naturally splits into multiple independent changes — "add X and Y and Z", "build the whole auth system", "migrate the service", or "do this task" when the scope clearly spans several discrete pieces. Orchestrates structured codebase exploration, change queue planning, isolated worktree execution per change, and spec verification. Prefer `opsx-ext:task` for single-change requests that don't need a queue or isolated worktrees. Skip for questions, explanations, bug fixes, single-line patches, console.log debugging, version bumps, and /opsx command runs.
Stoica-Mihai/claude-skills · ★ 0 · AI & Automation · score 76
Install: claude install-skill Stoica-Mihai/claude-skills
# Autonomous Task-Queue Workflow End-to-end orchestrator for OpenSpec. Takes a user's request, breaks it into a queue of discrete changes, and processes each one in an isolated git worktree — from planning through verified implementation — before handing back to the user for final review and commit. ## Core Principles 1. **Queue-first**: Break the request into discrete, independent changes before touching any code. 2. **Isolated execution**: Each change runs in its own git worktree so changes never interfere with each other. 3. **Verify before commit**: Each change is implemented and verified automatically, but only committed after the user reviews it. 4. **Parallel within, sequential across**: Maximize parallelization within each change's phases (spawn as many subagents as the work allows), but process changes one at a time through the queue. When dispatching subagents within a phase: - Launch all independent subagents in a single tool-call turn — do not wait between dispatches - Give each subagent a complete, self-contained prompt with all context it needs so it can work autonomously - Use background execution for subagents whose results are not blocking the next immediate action - Only serialize work when there is a true data dependency ## Hard Requirement OpenSpec must be initialized in the project. If the `openspec/` directory does not exist, stop immediately and tell the user to run `openspec init` and `openspec update` first. Do not proceed without this. ## Runn