amElnagdy/delegate-skills / skills/qoder-delegate
qoder-delegate
VerifiedDelegate a coding task to the Qoder CLI (`qodercli`) as a background implementer, then review its diff and land it yourself. Use this whenever the user asks to have Qoder implement, fix, refactor, or run a queue of coding tasks while the orchestrator remains the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants code written directly without delegation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.1 KB |
| references/dispatch-and-poll.md | markdown | 5.6 KB |
| references/multi-task-queues.md | markdown | 1.5 KB |
| references/review-and-land.md | markdown | 2.5 KB |
| references/writing-the-brief.md | markdown | 3.4 KB |
| scripts/relay.mjs | script | 25.1 KB |
references/multi-task-queues.md
View on GitHub# Multi-task queues
Scale the single-task loop through sequencing and bookkeeping, not a larger brief.
## Run sequentially
Dispatch one task, review it, rerun its gates, and land it before the next:
```bash
node "<skill-dir>/scripts/relay.mjs" --brief task-01.txt --cd /path/to/repo
```
- Later briefs can rely on earlier work only after it lands.
- One commit per task keeps review and rollback bounded.
- A clean tree makes `touchedFiles` useful.
- Parallelize only genuinely independent tasks in separate worktrees.
## Carry constraints forward
Fresh Qoder sessions do not know earlier queue decisions. Put any helper name, fixture location, or
interface needed later into the later brief.
Resume only for rework on the same task. Send a delta with `--resume-last` or `--resume <id>` from that
task's `result.json`. Start unrelated items in fresh sessions.
## Keep a progress file
For more than two or three tasks, track:
- queued / at-implementer / reviewed+committed status and commit hash;
- per-task review notes and gate outcomes;
- design choices and questions needing human review;
- the final cross-task verification.
Update it after every landed task.
## Close coherently
After the last task, run the full gates once more, search repository-wide for the changed concept,
round-trip migrations when applicable, and only then push or open a pull request.
Stop and ask if a task cannot fit its brief, review invalidates the plan, or gates reveal a problem in
already-landed work. Report the landed hashes and open question before waiting.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |