This skill should be used when the user has a large, complex task requiring: (1) multi-file or multi-step implementation, (2) major refactoring or architecture changes, (3) new feature spanning multiple components. This skill should NOT be used for simple fixes, single-file edits, or quick questions. Activates strict verification with planning, success criteria, and evidence collection.
Enforces verification-first development for complex multi-file tasks with strict evidence requirements.
npx claudepluginhub mnthe/hardworker-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/blocked-patterns.mdreferences/state-schema.mdreferences/verification-protocol.mdUltrawork enforces verification-first development - a strict mode where every completion claim requires concrete evidence.
PLANNING → EXECUTION → VERIFICATION → COMPLETE
↑ │
└── (Ralph Loop on fail) ←┘
| Phase | Description | Key Outputs |
|---|---|---|
| Planning | Explore → Design → Task decomposition | design.md, tasks/*.json |
| Execution | Workers implement tasks in parallel waves | Code changes, evidence |
| Verification | Verifier audits ALL evidence against criteria | PASS/FAIL decision |
Start ultrawork with the /ultrawork command:
/ultrawork "your goal" # Interactive: asks questions, user approves plan
/ultrawork --auto "your goal" # Auto: decides autonomously, no confirmations
/ultrawork --plan-only "goal" # Planning only, no execution
| Mode | Best For | User Interaction |
|---|---|---|
| Interactive (default) | Complex features, unclear requirements | Questions + approval |
Auto (--auto) | Well-defined tasks, CI/CD | None |
Plan-only (--plan-only) | Design review before implementation | Planning only |
USE ultrawork for:
DON'T use ultrawork for:
Verification automatically FAILS if output contains blocked patterns.
See references/blocked-patterns.md for complete list.
Common blocked phrases:
Every completion claim requires concrete proof.
| Claim | Required Evidence |
|---|---|
| "Tests pass" | npm test output with exit code 0 |
| "Build succeeds" | Build command output with exit code 0 |
| "Feature works" | Demo, test output, or screenshot |
| "Bug fixed" | Before/after comparison |
See references/verification-protocol.md for detailed verification requirements.
Each session has isolated state in ~/.claude/ultrawork/sessions/${CLAUDE_SESSION_ID}/.
See references/state-schema.md for complete schema documentation.
Key files:
session.json - Phase, options, metadatacontext.json - Exploration summariesexploration/*.md - Detailed findingstasks/*.json - Task definitions and evidence| Command | Purpose |
|---|---|
/ultrawork-status | Check current phase and progress |
/ultrawork-evidence | View collected evidence log |
/ultrawork-clean | Clean up sessions (interactive/all/stale) |
/ultrawork-exec | Execute existing plan |
/ultrawork-plan | Planning phase only |
references/blocked-patterns.md - Complete list of blocked phrases and whyreferences/verification-protocol.md - Detailed verification requirementsreferences/state-schema.md - Session and task JSON schemasActivates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.