plugins/cache/omc/oh-my-claudecode/4.8.2/skills/ultrawork/SKILL.md
Parallel execution engine for high-throughput task completion
npx skillsauth add moliboy5000/.claude ultraworkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
<Use_When>
<Do_Not_Use_When>
ralph instead (ralph includes ultrawork)autopilot instead (autopilot includes ralph which includes ultrawork)ralph which adds persistence on top of ultrawork
</Do_Not_Use_When><Why_This_Exists> Sequential task execution wastes time when tasks are independent. Ultrawork enables firing multiple agents simultaneously and routing each to the right model tier, reducing total execution time while controlling token costs. It is designed as a composable component that ralph and autopilot layer on top of. </Why_This_Exists>
<Execution_Policy>
model parameter explicitly when delegatingdocs/shared/agent-tiers.md before first delegation for agent selection guidancerun_in_background: true for operations over ~30 seconds (installs, builds, tests)<Tool_Usage>
Task(subagent_type="oh-my-claudecode:executor", model="haiku", ...) for simple changesTask(subagent_type="oh-my-claudecode:executor", model="sonnet", ...) for standard workTask(subagent_type="oh-my-claudecode:executor", model="opus", ...) for complex workrun_in_background: true for package installs, builds, and test suites<Escalation_And_Stop_Conditions>
ralph mode<Final_Checklist>
ralph (persistence wrapper)
\-- includes: ultrawork (this skill)
\-- provides: parallel execution only
autopilot (autonomous execution)
\-- includes: ralph
\-- includes: ultrawork (this skill)
Ultrawork is the parallelism layer. Ralph adds persistence and verification. Autopilot adds the full lifecycle pipeline. </Advanced>
tools
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
development
DEFAULT PIPELINE for all tasks requiring execution. You (Claude) are the strategic orchestrator. Codex agents are your implementation army - hyper-focused coding specialists. Trigger on ANY task involving code, file modifications, codebase research, multi-step work, or implementation. This is NOT optional - Codex agents are the default for all execution work. Only skip if the user explicitly asks you to do something yourself.
development
This skill should be used when the user asks to analyze a UI screen recording and map interaction states into Figma. Trigger for requests such as "put video frames in Figma", "extract states from my recording", "map interactions from video to Figma", "analyze this screen recording", "create a storyboard from my video", "deconstruct this interaction in Figma", "annotate the UI states in my recording", or "pull the key moments from this video into Figma". Also trigger when the user references a video file (.mp4, .mov, .webm, .avi) together with Figma, design review, interaction analysis, prototypes, or UI states. The skill extracts key visual moments from a video, infers interaction triggers, and builds an annotated Figma Design storyboard using native Figma annotations and uploaded screenshot assets.
development
Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.