hyper-implementlisted

# hyper-implement Plan execution gate. Reads a plan, dispatches a fresh subagent per task, runs two reviews (spec compliance, then code quality) before marking each task complete. Uses our own agents (`implementer`, `verifier`) and our own gate skills. ## When to use - User typed `/hyperclaude:hyper-implement [path]`. - A multi-task plan exists (typically in `.hyperclaude/plans/`) and you're about to execute it. Skip when: - The plan is one step — just do it directly. - Tasks are tightly coupled and benefit from shared context. - You're prototyping; reviews are overhead at this stage. ## How to invoke **Invocation argument:** $ARGUMENTS ### Step 1 — Resolve the plan path In priority order: 1. If $ARGUMENTS is non-empty, treat it as a path and use it. 2. Else, find the most recent plan via the Bash tool: ```bash ls -1t .hyperclaude/plans/*.md 2>/dev/null | head -1 ``` 3. If nothing found, tell the user: "No plan file found. Write your plan to `.hyperclaude/plans/<slug>.md` first." Stop. ### Step 1.5 — Reject epic roadmaps Read the resolved plan's opening lines. If the file begins with a YAML frontmatter block containing `tier: epic`, it is an epic **roadmap**, not an executable task plan (`hyper-plan` emits these for oversized tasks, under `.hyperclaude/epics/`). **STOP** before any branch or git work and tell the user, **substituting the resolved roadmap path** into the command: "This is an epic roadmap (`tier: epic`), not an executable task plan. Expand