ultrawork

Enforce verification-first development with planning, evidence, and deterministic execution loops.

4|Updated Jan 8, 2026

Search Tags:#planning #verification #evidence #team-collaboration #development-workflow #multi-file

Ready to run

npx skills add https://github.com/mnthe/hardworker-marketplace --skill ultrawork-mnthe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ultrawork
Source: https://github.com/mnthe/hardworker-marketplace/tree/main/plugins/ultrawork/skills/ultrawork
Command: npx skills add https://github.com/mnthe/hardworker-marketplace --skill ultrawork-mnthe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ultrawork enforces verification-first development, ensuring every completion claim is supported by an explicit plan and concrete evidence, reducing risk and rework on complex tasks.

Core Features & Use Cases

Mandatory planning with clearly defined success criteria to decompose large tasks.
Evidence-based completion requiring demonstrable outputs (tests, logs, demos) before marking work complete.
Plan → Execute → Verify loop with parallel task execution and session isolation.
Suitable for solo developers tackling complex features or teams coordinating multi-file work.

Quick Start

Start a session with /ultrawork "your goal", check status with /ultrawork-status, and view evidence with /ultrawork-evidence

Frequently Asked Questions about ultrawork

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce evidence-based verification for multi-file development workflows?▼

Evidence-based verification requires demonstrable outputs like tests or logs before marking work complete. You enforce this by running a deterministic Plan, Execute, and Verify loop that mandates success criteria and collects concrete evidence for every task.

What is verification-first development for complex software engineering tasks?▼

Verification-first development is a process requiring explicit planning and concrete evidence before task completion. It reduces rework on complex multi-file projects by enforcing a strict loop where every execution phase must produce demonstrable proof of success.

How do I plan and execute large team-collaboration tasks with mandatory success criteria?▼

Plan large team-collaboration tasks by decomposing goals into mandatory steps with clearly defined success criteria. Execute these steps using parallel task execution and session isolation, ensuring every completed item provides concrete evidence of success.

Does this verification-first approach work for solo developer multi-file projects?▼

Yes, this verification-first approach works for solo developer multi-file projects. It applies the same mandatory planning, evidence collection, and deterministic execution loops to individual workflows, ensuring complex features are completed with demonstrable proof.

What is the best way to collect evidence during a development workflow verification phase?▼

The best way to collect evidence during a development workflow is to require demonstrable outputs such as tests, logs, or demos. This ensures every completion claim is supported by concrete proof before the verification phase concludes.

Why does my multi-file development workflow lack deterministic verification and require rework?▼

Multi-file development workflows require rework when they lack deterministic verification loops and mandatory planning. Without enforced evidence collection and clearly defined success criteria, completion claims remain unverified, increasing risk and causing errors.