How do I install the Hyperflow Spec skill?

Run npx skillmds@latest add tuyv/hyperflow-spec 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 Spec safe to use?

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

Which AI agents work with Hyperflow Spec?

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 Spec free to use?

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

Who published Hyperflow Spec?

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

Hyperflow Spec by tuyv — Agent Skill

Name: Hyperflow Spec
Author: tuyv

Hyperflow Spec

Hyperflow design phase. Use when the user is exploring an idea, weighing approaches, or has an ambiguous request — verbs like brainstorm, design, explore, "should we", "what's the best way to", "unsure about". Thinking, not building. Produces an approved design at .hyperflow/specs/<slug>.md, then hands off to hyperflow-scope.

tuyv a61d4c8 4 files · 6.6 KB Updated Sep 17, 2026

File contents

hyperflow-spec — design phase (Antigravity single-agent)

This phase is thinking, not building. No code until the design is approved. Follow the hyperflow doctrine (autonomy, file-first, AskUserQuestion gates).

Steps

Research first. Read the relevant code, AGENTS.md, and .hyperflow/memory/* if present. Map the affected surface yourself. Do not ask what the code answers.
Ask 2-5 clarifying questions (floor: 2) via AskUserQuestion — only the what/which/where the code can't resolve. Multi-option questions mark one (Recommended); binary ones don't.
Propose 2-3 approaches with one-line pros/cons/fit each. Recommend one; let the user pick.
Design section-by-section. Write the design to .hyperflow/specs/<slug>.md with this shape: status table → TL;DR (2-3 sentences) → Components → 1. Architecture → 2. Data flow → 3. Key decisions (with trade-offs accepted/rejected) → 4. Edge cases → 5. File structure (created/modified). Present it; ask Approve all / Revise <section>.
On approval, hand off: invoke the hyperflow-scope skill with the spec path.

Rules

Never write implementation code here.
Never inflate a small task into a spec — economy matters. Trivial-clear requests skip straight to hyperflow-scope.
The spec file is the artefact; chat shows only a short pointer to it.

Frequently asked questions