hyper-plan-review

Evaluate Hyper task plans for completeness, alignment, and ownership.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews a Hyper feature-scope plan before implementation starts. It runs a calibrated, cross-artifact assessment across exploration.md, spec.md, and subtasks to surface risks, gaps, and ownership issues, producing a single plan-review.md with a verdict and recommended next steps.

Core Features & Use Cases

  • Evaluates completeness, spec-exploration alignment, task decomposition, ownership clarity, and edge cases; ensures no unresolved dependencies or broken references; supports provenance hygiene by validating plan references against the codebase.
  • Generates a structured plan-review.md at the task folder root containing a verdict (pass, needs-changes, blocked) and a recommended action (continue, fix-in-place, rethink). Enables faster decision-making in Hyper plan workflows.

Quick Start

Review a task folder's plan with hyper-plan-review to obtain a ready-to-use plan-review.md and a summarized verdict.

Frequently Asked Questions about hyper-plan-review

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

FAQPage Schema
How do I review a task plan for completeness and alignment before implementation?

You can review task plans by cross-checking exploration.md, spec.md, and subtasks to surface risks, validate codebase references, and output a plan-review.md containing a clear verdict and recommended next steps.

What is plan quality assessment for feature-scope tasks?

Plan quality assessment is the process of evaluating task decomposition, ownership clarity, and spec-exploration alignment to ensure a feature plan meets provenance and quality requirements before implementation begins.

How do I validate codebase-verification references in a spec document?

Validate codebase-verification references by checking that all paths and pointers within the spec.md and exploration.md artifacts correctly map to existing codebase locations, ensuring provenance hygiene and preventing broken references during implementation.

Does this plan review process support checking task ownership and edge cases?

Yes, the plan review process explicitly evaluates task ownership clarity and identifies edge cases, ensuring that all unresolved dependencies are surfaced and addressed before the implementation phase starts.

What is the best way to formalize a go or no-go decision for a feature plan?

The best way to formalize a go or no-go decision is to generate a structured plan-review.md that provides a standardized verdict of pass, needs-changes, or blocked, alongside a recommended action to continue, fix-in-place, or rethink.