hyper-verify
Runs the verify phase of a Hyper task. Three lenses in one pass, written to a single checks.md with a pass/needs-changes/blocked verdict. Runs the project's test suite (stabilize), reviews the diff for correctness and security issues (review), and verifies user-facing acceptance criteria against real behavior (QA). Use when a Hyper task is in the 'verify' phase, after implementation is done. Keywords: hyper, verify, tests, review, QA, code review, security review, checks.md.
Repository SourceNeeds Review
install-hyper
Installs, uninstalls, or checks the status of Hyper skills across every supported agent skill directory on this machine — Claude Code (~/.claude/skills/), Codex (~/.codex/skills/), ~/.agents/skills/, and PI (~/.pi/agent/skills/). Symlinks the skill folders from this repo so local edits take effect immediately. Use when the user asks to install Hyper, set up Hyper for testing, refresh the installed skills, uninstall Hyper, or check whether Hyper is installed. Only meaningful when Claude Code (or another agent) is running inside the hyper7 development repo. Keywords: install, hyper, setup, symlink, refresh, uninstall, status, codex, claude, pi.
Repository SourceNeeds Review
hyper-plan-review
Reviews a Hyper feature-scope plan (exploration.md + spec.md + subtask files) before implementation starts. Runs calibrated criteria across completeness, spec-vs-exploration alignment, task decomposition, done-when specificity, out-of-scope and edge cases, and buildability, plus a codebase-verification sub-step that classifies every file / function / pattern reference in the plan as EXISTING vs PROPOSED and verifies only the EXISTING set. Writes a single `plan-review.md` at the task folder root with a `pass | needs-changes | blocked` verdict and a `continue | fix-in-place | rethink` recommendation. Invoked by `hyper-plan` after self-review; not user-invocable. Keywords: hyper, plan review, spec, exploration, verdict, plan-review.md.
Repository SourceNeeds Review
hyper-plan
Runs the plan phase of a feature-scope Hyper task. Turns the approved exploration.md into a spec.md (acceptance criteria + ToC-style subtask index + out-of-scope + edge cases) and one file per vertical slice named `T<N>.<M>-<slug>.md` at the task folder root (each with status, depends, and what/why/done-when). Sets an approval gate for the user before implementation starts. Runs only for feature-scope tasks (quick and research skip planning). Keywords hyper, plan, spec, acceptance criteria, subtasks, subtask files, spec.md.
Repository SourceNeeds Review