ultrawork

Chain specify, open, and execute hooks into an automated development pipeline.

171|23|Updated Jan 21, 2026

Search Tags:#automation #development #hooks #skills #orchestration #pipeline #ultrawork

Ready to run

npx skills add https://github.com/team-attention/hoyeon --skill ultrawork-team-attention

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ultrawork
Source: https://github.com/team-attention/hoyeon/tree/main/skills/ultrawork
Command: npx skills add https://github.com/team-attention/hoyeon --skill ultrawork-team-attention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the need to manually orchestrate multi-step development pipelines by chaining planning, PR creation, and execution into a single command.

Core Features & Use Cases

Hooks-driven orchestration that automatically advances from specify to open to execute.
End-to-end automation of planning, PR drafting, and implementation across projects.
State tracking and interruption handling via stop hooks for robust long-running workflows.

Quick Start

Use the ultrawork skill to initiate an end-to-end automation for a new feature, e.g., '/ultrawork add dark mode'.

Frequently Asked Questions about ultrawork

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

FAQPage Schema

How do I automate a full software development pipeline from planning to execution?▼

Automating a full development pipeline requires chaining planning, PR creation, and execution into a single command. This workflow uses hooks-driven orchestration to automatically advance tasks from specification through implementation with minimal manual intervention.

What is hooks-driven orchestration for development pipelines?▼

Hooks-driven orchestration automatically advances development tasks through stages like specify, open, and execute. It uses stop hooks for state tracking and interruption handling, ensuring robust long-running workflows across software projects without manual stage transitions.

Do I need a specific environment to run automated development pipelines with hook-driven transitions?▼

Running automated development pipelines requires a skill orchestration environment that supports hook-driven transitions, state tracking, and inter-skill communication. This setup is necessary to perform automated planning, PR drafting, and implementation seamlessly.

How do I start end-to-end automation for a new software feature?▼

Start end-to-end automation for a new feature by initiating a single command like '/ultrawork add dark mode'. This triggers the automated workflow to handle specification, PR drafting, and task execution sequentially across the project.

Can I handle interruptions during long-running automated development workflows?▼

Long-running automated development workflows handle interruptions via stop hooks for state tracking. This mechanism ensures that the pipeline can manage pauses and resumes robustly, maintaining the state of the end-to-end planning and execution process.

ultrawork vs manual orchestration of development stages: what is the difference?▼

Manual orchestration requires developers to individually trigger specification, PR creation, and execution stages. Automated orchestration chains these steps into one seamless workflow using hooks, eliminating the need to manually advance the development pipeline across projects.