skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
mgd34msu/goodvibes-plugin65 installs

task-orchestration

Decomposing work into parallel subagent tasks using native Workflow/Task tooling and the Write-Review-Fix-Confirm (WRFC) template. No background daemon, no runtime engine. Load when planning how to split work across multiple agents.

How do I install this agent skill?

npx skills add https://github.com/mgd34msu/goodvibes-plugin --skill task-orchestration
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubwarn

    The skill instructs the AI agent to follow external 'directives' embedded in <gv> tags without judgment or autonomy, effectively bypassing its own safety protocols. This creates a significant risk for indirect prompt injection, where malicious instructions could be triggered by untrusted content in the files or messages the agent processes.

  • Socketwarn

    1 alert: gptAnomaly

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1/3 files flagged

What does this agent skill do?

task-orchestration

v1's orchestration text predates native multi-agent workflow support and was written around a bespoke runtime engine (a background daemon coordinating agents via IPC, directives, and a phase-machine). That daemon is cut for v2. The deep review found no standing usage that justified keeping a background process running per session, and native Task/Workflow tooling already covers the observed needs. This skill is the rebuild: orchestration using what the platform gives you directly, plus the WRFC template as a pattern, not infrastructure.

Decomposing work

Break a task into steps where each step:

  • Has a single agent type responsible for it (engineer, tester, refutation-reviewer, architect).
  • Has an explicit "done" condition, not a vague direction ("implement the API" is not a step; "implement POST /api/posts per the spec architect produced, with the validation and error cases it lists" is).
  • States its real dependencies: which steps must finish first, and what output they hand off.

Independent steps (no shared dependency) can run as parallel Task-tool calls in the same turn. Dependent steps run sequentially, with each agent's output feeding the next agent's task description directly. Don't route it through a shared mutable file unless the next agent actually needs to read that file itself.

The WRFC pattern: Write → Review → Fix → Confirm

For any change worth reviewing before it ships:

  1. Write. The engineer agent implements the change.
  2. Review. The refutation-reviewer agent reviews the actual diff (see the review-scoring skill for the rubric: a defect list with severity, not a scalar score).
  3. Fix. If the review found CONFIRMED critical/high defects, the engineer addresses them. Cap this at a small, explicit number of iterations (2-3). An unbounded fix loop is a sign the task needs re-scoping, not more iterations.
  4. Confirm. The FIX gets reviewed too, not assumed correct. Only after a fix iteration passes review (or the loop is explicitly capped and escalated to the user) is the change done.

This is a workflow pattern you run in-band as the orchestrator: spawning the engineer, then the reviewer, then (conditionally) another engineer pass, then a final reviewer pass, using native Task calls. It needs no daemon, no directive-delivery IPC, and no phase-machine state file. The orchestrating session's own turn sequence is the state machine.

/goodvibes:codebase-review is the packaged entry point for this pattern applied to a whole diff/PR. See that command for the concrete workflow.

When not to use the full loop

A one-line typo fix or a change with no meaningful failure surface doesn't need a dedicated review agent. Use judgment. WRFC earns its cost on changes where "did this actually work" is a real question, not on everything unconditionally (v1's automatic-review-on-every-agent behavior was one of the field-identified sources of wasted review cycles on read-only work).

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/mgd34msu/goodvibes-plugin/task-orchestration">View task-orchestration on skillZs</a>