What does 'Verification-First' mean?

It means the skill requires concrete evidence—such as successful build logs or passing test results—before any task is considered complete.

What happens if a task fails verification?

Ultrawork enters a loop where it analyzes the failure, adjusts the approach, and re-executes until the success criteria are met with proof.

Can I use Ultrawork without manual intervention?

Yes, using the --auto flag allows Ultrawork to make autonomous decisions and proceed through phases without requiring user confirmation.

When should I use Ultrawork instead of standard Claude Code commands?

Use Ultrawork for complex, multi-file tasks (3+ files) or architectural changes. Avoid it for simple bug fixes or single-file edits that take less than 5 minutes.

Ultrawork Verification-First Workflow

Name: Ultrawork Verification-First Workflow
Author: mnthe

bymnthe

•

Productivity & Workflow

Enforces a strict, verification-first development cycle for complex multi-file implementations and major architectural refactoring within Claude Code.

About

Ultrawork is a specialized skill for Claude Code designed to handle large-scale engineering tasks that demand high precision and accountability. By implementing a 'Planning-Execution-Verification' loop, it ensures that no implementation occurs without a design phase and no task is marked complete without verifiable evidence, such as test outputs or build logs. This skill is ideal for developers managing significant refactors or building new features across multiple components where 'basic implementations' or 'TODOs' are unacceptable, providing a zero-tolerance approach to partial or unverified code.

Key Features

2 GitHub stars
Zero-Tolerance for Placeholders: Automatically rejects code containing 'TODOs', 'should work', or simplified versions.
Structured Planning Phase: Mandatory codebase exploration and task decomposition before coding starts.
Multi-Wave Execution: Manages complex implementations spanning multiple files and architectural components.
Evidence-Based Verification: Requires concrete proof like command outputs or test results for every completion claim.
Isolated Session State: Maintains detailed logs of exploration, design decisions, and evidence in dedicated session directories.

Use Cases

High-stakes deployments where every change must be backed by a verified test trail.
Major architectural refactoring spanning three or more files.
Implementing new feature sets that require coordinated changes across multiple components.

About

Key Features

2 GitHub stars
Zero-Tolerance for Placeholders: Automatically rejects code containing 'TODOs', 'should work', or simplified versions.
Structured Planning Phase: Mandatory codebase exploration and task decomposition before coding starts.
Multi-Wave Execution: Manages complex implementations spanning multiple files and architectural components.
Evidence-Based Verification: Requires concrete proof like command outputs or test results for every completion claim.
Isolated Session State: Maintains detailed logs of exploration, design decisions, and evidence in dedicated session directories.

Use Cases

High-stakes deployments where every change must be backed by a verified test trail.
Major architectural refactoring spanning three or more files.
Implementing new feature sets that require coordinated changes across multiple components.