How do I install the Hyperflow Plan skill?

Run npx skillmds@latest add gabrielmoreira/hyperflow-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hyperflow Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hyperflow Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hyperflow Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hyperflow Plan?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hyperflow Plan by gabrielmoreira — Agent Skill

Name: Hyperflow Plan
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Hyperflow Plan

Hyperflow planning phase. Use when a request needs shaping before code — a rough prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. Verbs like plan, design, brainstorm, explore, "should we", "what's the best way to", scope, decompose, "plan out", "break down", "enhance this prompt". Thinking, not building. Writes an optional spec to .hyperflow/specs/<slug>.md and a task file to .hyperflow/tasks/<slug>.md, then hands off to hyperflow-dispatch.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

hyperflow-plan — planning phase (Antigravity single-agent)

Thinking, not building. The only writes are to .hyperflow/. Each phase skips itself when the request doesn't need it. Follow the hyperflow doctrine (autonomy, file-first, AskUserQuestion gates).

Steps

Amplify (skippable). If the prompt is rough, rewrite it into its strongest form — role · task · context · constraints · output spec. Skip when it's already specific. Never inflate a one-line ask into a spec.
Research first. Read the relevant code, AGENTS.md, and .hyperflow/memory/*. Map the affected surface yourself — do not ask what the code answers.
Design (skippable). For an open-ended request: ask ≥2 clarifying questions (what/which/where only), propose 2–3 approaches, then design section-by-section into .hyperflow/specs/<slug>.md with approval per section. A clear request bounces straight to decomposition. When a system, UI, motion, or mobile surface is in scope, ground the design in the matching standards (architecture decomposition + a diagram, the design system, the Motion language, the mobile platform/device matrix).
Decompose. Produce a topologically-ordered batch graph; each sub-task = one conventional-commit-sized change. Split any sub-task touching >5 files, >500 LOC, 2+ subsystems, or >10-min review. Write .hyperflow/tasks/<slug>.md: status table → Goal → Why → Scope-at-a-glance → Affected files → Execution plan → Batches (role, files, complexity, acceptance criteria, commit stub) → Verification plan.
Print Plan ready — .hyperflow/tasks/<slug>.md (N batches, M sub-tasks).
Hand off: invoke the hyperflow-dispatch skill with the task slug — or, in two-session mode, write a committed handoff package and stop.

Rules

No implementation code; no source edits.
Floor of 2 clarifying questions on the design path; 0–3 on the bounce (decompose-only) path.
Single-batch plans for multi-file work are an anti-pattern — decompose.
Always include a concrete verification plan.

---name: hyperflow-plandescription: Hyperflow planning phase. Use when a request needs shaping before code — a rough prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. Verbs like plan, design, brainstorm, explore, "should we", "what's the best way to", scope, decompose, "plan out", "break down", "enhance this prompt". Thinking, not building. Writes an optional spec to .hyperflow/specs/<slug>.md and a task file to .hyperflow/tasks/<slug>.md, then hands off to hyperflow-dispatch.--- # hyperflow-plan — planning phase (Antigravity single-agent) Thinking, not building. The only writes are to `.hyperflow/`. Each phase skips itself when the request doesn't need it. Follow the `hyperflow` doctrine (autonomy, file-first, AskUserQuestion gates). ## Steps 1. **Amplify (skippable).** If the prompt is rough, rewrite it into its strongest form — role · task · context · constraints · output spec. Skip when it's already specific. Never inflate a one-line ask into a spec. 2. **Research first.** Read the relevant code, `AGENTS.md`, and `.hyperflow/memory/*`. Map the affected surface yourself — do not ask what the code answers. 3. **Design (skippable).** For an open-ended request: ask ≥2 clarifying questions (what/which/where only), propose 2–3 approaches, then design section-by-section into `.hyperflow/specs/<slug>.md` with approval per section. A clear request bounces straight to decomposition. When a system, UI, motion, or mobile surface is in scope, ground the design in the matching standards (architecture decomposition + a diagram, the design system, the Motion language, the mobile platform/device matrix). 4. **Decompose.** Produce a topologically-ordered batch graph; each sub-task = one conventional-commit-sized change. **Split any sub-task** touching >5 files, >500 LOC, 2+ subsystems, or >10-min review. Write `.hyperflow/tasks/<slug>.md`: status table → Goal → Why → Scope-at-a-glance → Affected files → Execution plan → Batches (role, files, complexity, acceptance criteria, commit stub) → Verification plan. 5. **Print** `Plan ready — .hyperflow/tasks/<slug>.md (N batches, M sub-tasks)`. 6. **Hand off**: invoke the `hyperflow-dispatch` skill with the task slug — or, in two-session mode, write a committed handoff package and stop. ## Rules - No implementation code; no source edits. - Floor of 2 clarifying questions on the design path; 0–3 on the bounce (decompose-only) path. - Single-batch plans for multi-file work are an anti-pattern — decompose. - Always include a concrete verification plan.

Frequently asked questions