skills.rest
zeikar
zeikarCOMMUNITY
Explore all skills by this author →
Website𝕏@zeikar_devGitHub

hyper-plan-review

Critique existing implementation plans with Codex and save review artifacts.

3|Updated May 10, 2026
Search Tags:#implementation planning#codex#agent workflow#documentation sync#plan review#workspace safety#resume artifacts
One-click install
npx skills add https://github.com/zeikar/hyperclaude --skill hyper-plan-review-zeikar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hyper-plan-review
Source: https://github.com/zeikar/hyperclaude/tree/main/skills/hyper-plan-review
Command: npx skills add https://github.com/zeikar/hyperclaude --skill hyper-plan-review-zeikar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) components.

What problem does it solve?

Prevents wasted effort and risky execution by getting a focused Codex critique of an already-created implementation plan before changes are run.

Core Features & Use Cases

  • Plan sanity check: Reviews an existing plan file (typically in .hyperclaude/plans/) to identify blockers and required adjustments.
  • Codex plan-specific critique: Distinguishes plan review from code review by routing the plan to Codex for critique rather than implementation review.
  • Review artifact + iterative refinement: Saves the critique to .hyperclaude/plan-reviews/<timestamp>-<slug>.md and supports refining the plan using --resume when desired.

Quick Start

Run /hyperclaude:hyper-plan-review after you generate a plan to get Codex’s critique and update the plan before proceeding.

Frequently Asked Questions about hyper-plan-review

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

FAQPage Schema
How do I critique an implementation plan before executing it?▼

To critique an implementation plan, you route the existing plan file to Codex for a focused review. This identifies blockers and required adjustments, saving the critique as a markdown artifact for informed execution.

What is the best way to review a plan stored in .hyperclaude/plans/?▼

Reviewing a plan in .hyperclaude/plans/ involves invoking a codex bridge with a plan-review command. The system locates the file, generates a JSON-derived critique, and saves the review artifact with a timestamped slug.

Can I resume and refine a plan after generating a Codex critique?▼

Yes, you can resume and refine a plan after a Codex critique by using the --resume flag. This provides plan-path keyed continuity, allowing you to iteratively update the implementation based on the saved review artifact.

Do I need Node.js to run a Codex plan review?▼

Yes, you need Node.js installed as a prerequisite to run the Codex plan review. The Skill relies on Node scripts, specifically a codex bridge module, to invoke the critique process and handle the review artifacts.

How does plan review differ from code review in agent workflows?▼

Plan review differs from code review by routing the implementation strategy to Codex for critique rather than evaluating written code. This prevents wasted effort by detecting blockers in the plan before execution begins.

Related Skills

Explore More Software Engineering Skills→
akiojinakiojin
8

plan-scripts

Create, read, update, and delete coding plan files under CODEX_HOME/plans.

Community
Advanced
abcnutsabcnuts
60

executing-plans

Execute implementation plans in batches with review gates and safety checks.

Community
Advanced
cyberAlchemyAIcyberAlchemyAI
20

invoke-example-runner

Execute invoke template validation prompts in Codex and save Invoke Results.

Official
Advanced
liuminxin45liuminxin45
95

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency before implementation.

Community
Advanced