ultrawork

Automate approved requirement derivation and implementation execution from a single command.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/sr-ai-dev/sr-harness --skill ultrawork-sr-ai-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultrawork
Source: https://github.com/sr-ai-dev/sr-harness/tree/main/skills/ultrawork
Command: npx skills add https://github.com/sr-ai-dev/sr-harness --skill ultrawork-sr-ai-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the overhead of manually stepping through requirements discovery and then converting approved specs into working implementations.

Core Features & Use Cases

  • One-command ultrawork mode: starts an automated pipeline that chains specify and execute for a named feature.
  • Approval-gated workflow: advances through specify layers until the user approves the generated spec, then automatically triggers execution.
  • Spec-to-plan separation (v2): produces spec.json containing only requirements/sub-requirements and verification journeys, while execute derives and runs a sibling plan.json.
  • Interactive mode selection: execution prompts the user for dispatch/work/verify mode using AskUserQuestion rather than requiring CLI flags.
  • Interruptible operations: supports stopping/pausing/waiting mid-run for manual control.

Quick Start

Run the ultrawork pipeline by telling the assistant to execute "/ultrawork add dark mode support".

Frequently Asked Questions about ultrawork

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

FAQPage Schema
How do I automate requirements gathering and code generation into a single pipeline?

Automating requirements gathering and code generation requires a workflow that chains specification approval with task execution. You can use an automated pipeline to derive an approved spec and then automatically trigger the corresponding implementation tasks from a single command.

What is the best way to convert an approved specification into an execution plan?

Converting an approved specification into an execution plan is handled by separating spec-to-plan derivation. The process produces a spec.json containing requirements and verification journeys, then derives a sibling plan.json to execute the actual implementation tasks.

Can I pause pipeline automation mid-run for manual approval?

Pausing pipeline automation mid-run is supported through approval-gated workflows. The pipeline advances through specification layers until you approve the generated spec, and it supports stopping or waiting mid-run for manual control before proceeding.

How do I execute implementation tasks without passing CLI flags?

Executing implementation tasks without CLI flags is possible using interactive mode selection. During the execution flow, the system prompts you for dispatch, work, or verify modes using interactive questions rather than requiring command-line arguments.

Does the specify and execute workflow generate traceable requirement files?

The specify and execute workflow generates traceable requirement files by producing an approved spec-v2. This specification file is output to a designated directory to satisfy traced workflow requirements before automatically triggering the execution phase.