ultrawork-loop

Resolve pull request fixes and file-based todos before workflow progression.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/hackefeller/ghostwire --skill ultrawork-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultrawork-loop
Source: https://github.com/hackefeller/ghostwire/tree/main/.github/skills/ultrawork-loop
Command: npx skills add https://github.com/hackefeller/ghostwire --skill ultrawork-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guarantees that all outstanding work items, such as pull request fixes and file-based todos, are resolved before a workflow progresses to subsequent stages.

Core Features & Use Cases

  • Deterministic Drain: Acts as a reliable checkpoint to ensure all tasks are completed.
  • PR and Todo Resolution: Specifically targets and resolves pending pull request updates and internal to-do items.
  • Completion Handshake: Emits a clear signal (DONE) upon successful completion, allowing downstream processes to continue.
  • Use Case: After code changes are made, this Skill ensures all related PRs are merged and any inline code comments are addressed before the build or deployment phase begins.

Quick Start

Execute the ultrawork-loop skill to resolve all pending PRs and todos.

Frequently Asked Questions about ultrawork-loop

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

FAQPage Schema
How do I ensure all pull request fixes and file-based todos are resolved before workflow progression?

To ensure pull request fixes and file-based todos are resolved before workflow progression, use a deterministic drain checkpoint that sequentially resolves outstanding tasks and blocks downstream processes until a completion signal is emitted.

What is a deterministic workflow drain and when do I need it for code changes?

A deterministic workflow drain is a checkpoint mechanism that guarantees all outstanding work items are resolved before signaling progression. You need it after code changes to ensure related PRs are merged and inline code comments are addressed before the deployment phase begins.

How do I signal successful completion of pending PR and todo resolution to a downstream harness?

To signal successful completion of pending PR and todo resolution to a downstream harness, you must emit an explicit completion promise using the exact string `--completion-promise "DONE"` for harness recognition.

Can I use a workflow checkpoint to block the build phase until inline code comments are addressed?

Yes, you can use a workflow checkpoint to block the build phase until inline code comments are addressed. The checkpoint orchestrates the sequential resolution of file-based todos and PR updates, preventing subsequent stages from executing prematurely.

Does the workflow drain require any external dependencies or specific environment setup?

No, the workflow drain requires no external dependencies or specific environment setup. It operates as a standalone checkpoint that orchestrates task resolution and emits the required completion signal natively.