From dispatch
Generate images by dispatching one brief concurrently to every usable image-capable external agent, presenting all results as options with artifact paths, and remembering login and quota failures so a failed agent is never dispatched to again until its record clears. Use whenever the user asks for image generation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dispatch:image-generationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Announce at start:** "Generating images across the available agents."
Announce at start: "Generating images across the available agents."
The image-capable agents are codex and agy — two external agent CLIs whose models generate images. Everything about reaching them lives in this plugin's use-external-agents skill: the router that launches them, the brief contract they are dispatched under, and the matrix call that reports whether each one is installed and usable right now. Dispatching to all of them concurrently returns several candidate images, so the user picks instead of settling.
use-external-agents skill before anything else — this skill builds on its router, its task brief contract, and its facts-before-use matrix call, and does not restate them.${TMPDIR:-/tmp}/dispatch-image-generation/failures.json — a JSON array of {agent, reason, at} entries this skill maintains; a missing file is an empty record. Skip every agent it lists. If the record leaves no agent, report that and stop — clearing the record is the user's call.TAGS: image-generation, AGENTS: the image-capable agents not in the failure record, and a ## Response section demanding explicit ARTIFACT_PATH: lines.{agent, reason, at} entry to the failure record before doing anything else — the next generation must never dispatch to that agent.MUST:
ARTIFACT_PATH: line through verbatim.MUST NOT:
npx claudepluginhub wezzard/skills --plugin dispatchGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.