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.
Allowed Tools
No tools specified
Provided by Plugin
hyperflow
Fifteen specialized slash commands turn one Claude session into a structured multi-agent engineering pipeline. Thinking models orchestrate, triage, and review; worker models execute in parallel — every step is a Worker → Reviewer pair, and every non-trivial phase fans into sub-phases with their own reviewers. Auto-routing is on by default — say 'audit the diff', 'debug this test', 'large migration', or 'run a workflow' and the orchestrator routes to the right skill without the /hyperflow:* prefix. /hyperflow:workflow uses Claude Code dynamic workflows for big tasks and a portable Codex/OpenCode adapter where native workflows are unavailable; /hyperflow:spec asks the questions a senior engineer would; /hyperflow:scope decomposes into a batched task graph; /hyperflow:dispatch fans out persona-stitched workers under tiered review; /hyperflow:amplify rewrites a rough prompt into a high-quality one before you run it. 15 composable personas, 6 adaptive flow profiles, and persistent project memory compound across sessions. Works across Codex App/CLI, Claude Code, OpenCode, and Antigravity.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plusClick to copy
Instructions
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/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.md Approve all / Revise. - On approval, hand off: invoke the
hyperflow-scopeskill 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.