hyper-worker

Complete a dispatched subtask end-to-end with research, implementation, testing, and recording.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyper-worker
Source: https://github.com/galatanovidiu/hyper7/tree/main/skills/hyper-worker
Command: npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables an autonomous sub-agent to complete a single dispatched subtask end-to-end: research, implement, test, and record results, flipping the subtask to done.

Core Features & Use Cases

  • Executes one subtask slice end-to-end inside a dispatched sub-agent, coordinating with the parent task and spec.md.
  • Researches the given subtask, implements only the slice, runs tests, and records a Completion narrative.
  • Not user-invocable; runs under the hyper-implement orchestrator to ensure traceable progress and status updates.

Quick Start

Provide the subtask file path to the hyper-implement orchestrator to begin the end-to-end subtask workflow.

Frequently Asked Questions about hyper-worker

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

FAQPage Schema
How do I automate subtask execution end-to-end for a larger implementation task?

An autonomous sub-agent completes a dispatched subtask by researching, implementing, testing, and recording the result. It coordinates with the parent task and spec.md to ensure traceable progress and status updates.

What is the best way to ensure traceable progress when dispatching implementation subtasks?

Ensuring traceable progress involves appending a Completion narrative and updating the subtask status upon successful validation. Edits are constrained to declared writes, guaranteeing the subtask slice is recorded for traceability.

How does a subtask worker coordinate with a parent task and spec.md?

A subtask worker coordinates with a parent task and spec.md by using the given subtask file path to guide its work. It researches the slice, implements only the declared writes, and records a Completion narrative for the parent task.

Can I manually invoke a subtask worker to process a single implementation slice?

No, this subtask worker is not user-invocable. It runs exclusively under the hyper-implement orchestrator, which dispatches the subtask file path and manages the end-to-end workflow to ensure traceable status updates.

Why are edits constrained to declared writes during subtask implementation?

Edits are constrained to declared writes to maintain strict scope boundaries for the dispatched subtask. This ensures the sub-agent only implements its specific slice, preventing unauthorized modifications before the subtask status is updated to done.