amElnagdy/delegate-skills / skills/vibe-delegate
vibe-delegate
VerifiedDelegate a coding task to the Mistral Vibe CLI (`vibe`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Vibe — phrasings like "have Vibe implement X", "delegate this to Vibe", "run it through Mistral Vibe", "use vibe to implement/fix/refactor" — or wants to run a queue of coding tasks through Vibe while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| references/dispatch-and-poll.md | markdown | 7.8 KB |
| references/multi-task-queues.md | markdown | 2.3 KB |
| references/review-and-land.md | markdown | 4.0 KB |
| references/writing-the-brief.md | markdown | 5.5 KB |
| scripts/relay.mjs | script | 27.5 KB |
references/multi-task-queues.md
View on GitHub# Multi-task queues
The single-task loop scales to a queue: a removal across layers, a migration across files, or a
refactor sweep. Sequencing and bookkeeping make it trustworthy.
## Run sequentially, one commit per task
Run tasks **one at a time, in dependency order**, landing each after review and gates before
dispatching 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 history reviewable and each step revertible.
- A clean tree before each dispatch keeps `touchedFiles` honest.
Use parallel runs only for genuinely independent tasks in separate working trees. Sequential is the
default because it preserves clean task boundaries.
## Carry decided constraints forward
Fresh Vibe sessions do not remember earlier tasks. If task 2 chooses a helper name, fixture location,
or interface that task 5 needs, write that fact into task 5's brief.
Use a resumed Vibe session only for rework on the same task. Send a delta brief with `--resume-last`;
use `--session <id>` only for an id obtained outside the relay because Vibe's stream does not expose
one. Start unrelated queue items in fresh sessions.
## Keep a progress file
For more than two or three tasks, maintain one progress file beside the work:
- **Status table** — queued / at-implementer / reviewed+committed, with the commit hash.
- **Per-task review notes** — what landed, what you verified, and gate outcomes.
- **Needs your eyes** — design decisions, non-blocking nitpicks, and questions for the human.
- **End-of-run checklist** — the final cross-task verification.
Update it when each task lands, not in one batch at the end.
## Close with a coherence check
After the last task:
- Run the full test/build once more.
- Search repo-wide for the thing the queue changed.
- Replay migrations from a clean state and check drift when applicable.
- Push and open or update the PR only after the final tree is coherent.
## When to stop and ask
Proceed on work that follows from the agreed plan. Stop and surface when:
- A task cannot be completed correctly within its brief.
- Review calls the plan itself into question.
- Gates reveal a problem affecting already-landed tasks.
Report the landed state, commit hashes, and open question, then wait.
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: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |