Individual skill
ultrawork
This skill should be used when the user says "/ultrawork", "ultrawork", or wants to run the full specify → execute pipeline automatically with a single command. Automated end-to-end workflow that chains specify and execute skills.
skills/ultrawork/SKILL.md
Source commit 7cff03298928d128c70c9ea45052102ba6b1a0ea
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 173
- Repository last updated
- May 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- operations Derived category
- testing Derived category
- testing-browser Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,715 bytes
Read excerpt
# /ultrawork Skill - Automated Development Pipeline
You are initiating an **ultrawork** session — a fully automated pipeline that chains:
1. `/specify` — Systematic requirements derivation producing `requirements.md`
2. `/blueprint` — Contract-first planning producing `plan.json` from requirements
3. `/execute` — Reads `plan.json`, dispatches workers, and implements
## How It Works
The ultrawork pipeline runs automatically through **Stop hooks**:
- When specify finishes L4 with user approval → Hook triggers `/execute {spec-path}`
- `/execute` then derives `plan.json` from the approved spec and runs tasks to completion
- When all tasks complete → Pipeline ends
