hyper-implement

Execute multi-task engineering plans with per-task subagents and review gates.

3|Updated May 10, 2026
One-click install
npx skills add https://github.com/zeikar/hyperclaude --skill hyper-implement-zeikar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyper-implement
Source: https://github.com/zeikar/hyperclaude/tree/main/skills/hyper-implement
Command: npx skills add https://github.com/zeikar/hyperclaude --skill hyper-implement-zeikar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents fragile or scope-drifting code changes by executing a multi-task plan with mandatory spec compliance and code-quality reviews between tasks, then committing each completed task safely.

Core Features & Use Cases

  • Plan-driven execution: Resolves the plan path and extracts each task block from a plan stored under .hyperclaude/plans/.
  • Per-task subagent workflow: Runs a fresh implementer subagent for each task, followed by spec compliance review and code quality review before proceeding.
  • Safety and guardrails for commits: Enforces a clean-tree preflight and creates/uses a hyper/<slug> feature branch for per-task commits without pushing.

Quick Start

Run hyper-implement on your latest plan by invoking /hyperclaude:hyper-implement with no path argument.

Frequently Asked Questions about hyper-implement

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

FAQPage Schema
How do I execute multi-task engineering plans with automated code review?

To execute multi-task engineering plans with automated code review, this skill runs each task in an isolated subagent and gates progress with spec compliance and code-quality reviews before proceeding. It commits each completed task safely to a feature branch without pushing.

How does plan execution ensure spec compliance and prevent scope drift?

Plan execution ensures spec compliance by applying a fresh implementer subagent for each task, followed by mandatory spec compliance review and code quality review. It enforces repeated fix loops until reviewers approve, preventing fragile or scope-drifting changes from advancing.

Do I need a clean git tree before running automated plan execution?

Yes, automated plan execution requires a clean git tree before starting. The skill enforces a clean-tree preflight validation and creates or uses a dedicated hyper/<slug> feature branch to commit each completed task safely.

Can I run test verification during task-by-task code generation?

Yes, you can run test verification during task-by-task code generation when tests or build steps change. The skill applies optional test verification alongside spec compliance and code-quality reviews between tasks.

What is the best way to automate git commits for multi-task plans without pushing?

The best way to automate git commits for multi-task plans without pushing is to use a gated subagent workflow. This skill commits each completed task to a local hyper/<slug> feature branch and strictly enforces no pushing of branches or tags.

Where should plan files be stored for automated subagent workflow execution?

Plan files should be stored under the .hyperclaude/plans/ directory for automated subagent workflow execution. The skill resolves the plan path and extracts each task block from this location to begin implementation.