Orchestrate Hyper implement phases by batching subtask workers and remediation passes.
npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-implement
Please help me install this Agent Skill. Skill: hyper-implement Source: https://github.com/galatanovidiu/hyper7/tree/main/skills/hyper-implement Command: npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-implement
Implementing a Hyper task requires coordinating subtask work, batching, and remediation steps during the implement phase. This skill provides an orchestrator to manage per-subtask workers, select the next unblocked batch, dispatch work to capable harnesses, and advance the task state.
Initiate the implement phase by loading this skill and supplying a task folder containing task.md, exploration.md, spec.md, and all T<N> subtasks, then await worker progress to verification.
High-intent search queries and answers about installing and using this skill.
To coordinate parallel subtask implementation, an orchestrator scans task folders for subtask files, selects the next unblocked batch, and dispatches work to eligible harnesses. It manages status transitions and updates task frontmatter as workers complete their assignments.
Handling blocked verification passes involves routing quick-scope tasks through remediation passes defined in checks.md. The orchestrator updates task frontmatter, records blockers for human review, and passes control back to verify once the remediation steps are complete.
Dispatching implementation batches requires the orchestrator to scan the task folder for inputs and identify the next unblocked batch. It then dispatches subtasks to eligible harnesses, running them in parallel when possible or sequentially when dependencies require it.
Yes, task orchestration requires specific subtask file naming conventions. Feature-scope tasks must use files named T<N>.<M>-<slug>.md, while quick-scope tasks use remediation paths, ensuring the orchestrator can correctly identify, batch, and dispatch subtasks.
To initiate the implement phase, the task folder must contain task.md, exploration.md, spec.md, and all relevant T<N> subtask files. The orchestrator scans these inputs to select unblocked batches and dispatch work to capable harnesses.
Yes, the orchestrator manages both feature-scope and quick-scope task workflows. It coordinates multiple subtasks and status transitions for feature-scope tasks, while handling quick-scope tasks via remediation passes from checks.md and returning control to verify.
galatanovidiuGenerates spec.md and T<N>.<M>-<slug>.md files from Chest. .md inputs.
spacholski1225Execute implementation plans in controlled batches with human review checkpoints.
KuassExecute predefined implementation plans in batches with review checkpoints.
phj128Automate end-to-end implementation tasks with a state-machine workflow and quality gates.
