ultrawork

Enforces a certainty-gated, TDD-driven orchestration workflow with mandatory verification for coding tasks.

Updated Jul 31, 2024
One-click install
npx skills add https://github.com/sharosoo/dotfile --skill ultrawork-sharosoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ultrawork
Source: https://github.com/sharosoo/dotfile/tree/main/omp/omo-layer/skills/ultrawork
Command: npx skills add https://github.com/sharosoo/dotfile --skill ultrawork-sharosoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents AI coding agents from shipping partial, unverified, or assumption-based work by enforcing an absolute-certainty gate, mandatory planning, test-driven development, and manual QA before any task is declared done. ## Core Features & Use Cases - Absolute-certainty gate: Blocks implementation until requirements are fully understood, the codebase is explored, and all ambiguity is resolved. - Mandatory plan-agent orchestration: Delegates non-trivial tasks to a planning agent and executes the returned wave order, delegating work to specialist agents (explore, librarian, oracle, hephaestus, designer). - TDD red-green-surface workflow: Requires a failing test first, the smallest passing change, then a real-surface artifact (bash, curl, browser) proving the feature works. - Manual QA mandate: Rejects "tests pass" or "lsp clean" as sufficient evidence and demands end-to-end verification with cleanup of spawned resources. - Use Case: When implementing a new API endpoint, the agent writes a failing test, implements the minimal fix, curls the endpoint to capture the real response, and tears down any test resources before reporting completion. ## Quick Start Activate ultrawork mode with /ultrawork and ask the agent to implement your feature with full test-driven verification.

Frequently Asked Questions about ultrawork

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

FAQPage Schema
How do I activate ultrawork mode?▼

Activate ultrawork mode with the /ultrawork command. The agent confirms activation by responding with "ULTRAWORK MODE ENABLED!" and then applies the full certainty-gate, planning, and TDD workflow to subsequent tasks.

How does the ultrawork TDD workflow work?▼

The workflow follows RED, GREEN, SURFACE: write a failing test first and capture the failure, implement the smallest change that makes it pass, then exercise the real surface such as a bash command, curl request, or browser interaction and capture that artifact as proof.

When is the plan agent invocation mandatory?▼

The plan agent is mandatory for any non-trivial task, defined as work with two or more steps, unclear scope, required implementation, or an architecture decision. The agent executes the returned plan in its exact wave order and parallel grouping.

Why is "tests pass" not accepted as verification?▼

Tests are the floor, not the ceiling. The methodology requires a real-surface artifact showing what the user actually sees, such as CLI output, an HTTP response, or a browser screenshot, because test suites and type checks do not catch functional bugs.

What tasks are exempt from the test-first requirement?▼

Exemptions cover pure formatting, comment-only changes, dependency bumps with no behavior delta, and rename-only refactors. Each exemption must be justified in the Findings section, and unjustified exemptions are rejected.