Agent Skills: 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.
ID: mgd34msu/goodvibes-plugin/task-orchestration
63
Install this agent skill to your local
Skill Files
The files that make up task-orchestration.
More agent skills
- desktop-releaseCut and publish ryOS Electron desktop releases on GitHub. Covers bumping package.json version, tagging v*, triggering Build Electron, and verifying the GitHub release. Use when the user asks to release the desktop app, bump the desktop version, trigger an Electron build, or publish macOS/Windows installers.
- wardenRun Warden to analyze code changes before committing. Use when asked to "run warden", "check my changes", "review before commit", "warden config", "warden.toml", "create a warden skill", "add trigger", or any Warden-related local development task.
- ui-designerExtract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.
- project-session-managerWorktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
- agent-experienceAudit the developer experience of a product, SDK, docs site, or SKILL.md by dropping multiple Claude subagents at it with only a tiny task prompt and real tools (WebFetch, Bash, Write). Agents must discover the docs themselves, install deps, ask for credentials if needed, and attempt real execution. The skill captures each agent's trace — tool calls, retries, wall time, errors — and scores on Setup Friction, Speed, Efficiency, Error Recovery, and Doc Quality, then emits an HTML report with an A–F grade and concrete fixes. Use when the user asks to audit agent experience, test a skill, audit docs for agents, check if a SDK is agent-friendly, validate a SKILL.md, measure agent DX, or benchmark how painful onboarding is for an AI agent. Triggers: 'audit agent experience', 'test this skill', 'audit docs for agents', 'is my SDK agent-friendly', 'run a DX audit', 'agent experience test', 'test my docs', 'how do agents do with my product'.
- ask-questions-if-underspecifiedClarify requirements before implementing. Do not use automatically, only when invoked explicitly.