hyper-plan-loop

Iteratively generate, critique, and revise engineering plans until blocking issues are removed.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the uncertainty of whether a generated engineering plan is correct and implementable by repeatedly running Codex critique and revising the plan until blocking issues are gone.

Core Features & Use Cases

  • Autonomous plan hardening loop: Generates a plan, runs Codex plan-review, and revises until Codex finds no blocking findings.
  • Live planner with persistent context: Spawns a planner teammate once and reuses its retained planning context across revise rounds.
  • Meaning-based gating: Treats findings as blocking based on whether they affect plan-level correctness, not Codex severity labels.
  • Resumable, artifact-driven workflow: Writes canonical plan artifacts to .hyperclaude/plans for review and continuity.

Quick Start

Use /hyperclaude:hyper-plan-loop add OAuth login to the API to generate a plan, review it with Codex, and revise it until it’s clean.

Frequently Asked Questions about hyper-plan-loop

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

FAQPage Schema
How do I automatically validate and revise an engineering plan until it is ready?

Autonomous plan hardening works by spawning a live planner teammate that generates a plan, then repeatedly running Codex plan-review and revising the artifact until no blocking findings remain.

What is the best way to run iterative plan critique with a persistent planning context?

Iterative plan critique uses a live planner teammate spawned once and reused across revise rounds, retaining its planning context to ensure continuity throughout the plan hardening workflow.

How does meaning-based gating work when reviewing a generated software plan?

Meaning-based gating treats Codex findings as blocking only if they affect plan-level correctness, ignoring generic severity labels to focus on issues that actually prevent implementation.

Do I need an agent-teams setup to run an autonomous plan review and revision loop?

Yes, this resume-aware plan hardening workflow requires an experimental agent-teams setup to spawn the live planner teammate and execute the codex-bridge plan-review iterations.

Where are engineering plan artifacts stored during a resumable plan hardening workflow?

Plan artifacts are written to a canonical plan path within the .hyperclaude/plans directory, enabling artifact-driven validation, review, and workflow continuity across multiple revise rounds.

Can I inline research artifacts into a generated plan during the revision loop?

Yes, optional research artifact inlining is supported through slug matching, allowing you to integrate external research directly into the plan during the iterative critique and revision process.