ultrawork

yeachan-heo/oh-my-claudecode · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill ultrawork
0 commentsdiscussion
summary

<Use_When>

skill.md

<Use_When>

  • Multiple independent tasks can run simultaneously
  • User says "ulw", "ultrawork", or wants parallel execution
  • You need to delegate work to multiple agents at once
  • Task benefits from concurrent execution but the user will manage completion themselves </Use_When>

<Do_Not_Use_When>

  • Task requires guaranteed completion with verification -- use ralph instead (ralph includes ultrawork)
  • Task requires a full autonomous pipeline -- use autopilot instead (autopilot includes ralph which includes ultrawork)
  • There is only one sequential task with no parallelism opportunity -- delegate directly to an executor agent
  • User needs session persistence for resume -- use 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>

  • Fire all independent agent calls simultaneously -- never serialize independent work
  • Always pass the model parameter explicitly when delegating
  • Read docs/shared/agent-tiers.md before first delegation for agent selection guidance
  • Use run_in_background: true for operations over ~30 seconds (installs, builds, tests)
  • Run quick commands (git status, file reads, simple checks) in the foreground </Execution_Policy>

<Tool_Usage>

  • Use Task(subagent_type="oh-my-claudecode:executor", model="haiku", ...) for simple changes
  • Use Task(subagent_type="oh-my-claudecode:executor", model="sonnet", ...) for standard work
  • Use Task(subagent_type="oh-my-claudecode:executor", model="opus", ...) for complex work
  • Use run_in_background: true for package installs, builds, and test suites
  • Use foreground execution for quick status checks and file operations </Tool_Usage>

<Escalation_And_Stop_Conditions>

  • When ultrawork is invoked directly (not via ralph), apply lightweight verification only -- build passes, tests pass, no new errors
  • For full persistence and comprehensive architect verification, recommend switching to ralph mode
  • If a task fails repeatedly across retries, report the issue rather than retrying indefinitely
  • Escalate to the user when tasks have unclear dependencies or conflicting requirements </Escalation_And_Stop_Conditions>

<Final_Checklist>

  • All parallel tasks completed
  • Build/typecheck passes
  • Affected tests pass
  • No new errors introduced </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.

how to use ultrawork

How to use ultrawork on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add ultrawork
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill ultrawork

The skills CLI fetches ultrawork from GitHub repository yeachan-heo/oh-my-claudecode and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ultrawork

Reload or restart Cursor to activate ultrawork. Access the skill through slash commands (e.g., /ultrawork) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.759 reviews
  • Kwame Rao· Dec 28, 2024

    ultrawork has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Omar Torres· Dec 20, 2024

    Useful defaults in ultrawork — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Lucas Li· Dec 16, 2024

    ultrawork reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Mia Lopez· Dec 12, 2024

    We added ultrawork from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Liam Perez· Dec 8, 2024

    Solid pick for teams standardizing on skills: ultrawork is focused, and the summary matches what you get after install.

  • Omar Patel· Nov 23, 2024

    We added ultrawork from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Omar Sanchez· Nov 19, 2024

    ultrawork reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Camila Sethi· Nov 11, 2024

    I recommend ultrawork for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Omar Flores· Nov 7, 2024

    ultrawork has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Camila Brown· Oct 26, 2024

    Useful defaults in ultrawork — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 59

1 / 6