Advanced multi-agent orchestration with persistent cross-session memory, per-step multi-level review, persona stitching, and adaptive flow profiles
MIT License
Free Pricing
Installation

Open Claude Code and run this command:
/plugin install hyperflow@claude-code-plugins-plus
Use --global to install for all projects, or --project for current project only.
What It Does

Hyperflow — init once with scaffold, then the chain: amplify → spec → scope → dispatch → audit → deploy, with thinking/worker tiers and a Worker → Reviewer review at every step
Hyperflow

Multi-agent orchestration for Codex App/CLI, Claude Code, OpenCode & Antigravity.
Thinking models plan and review every step. Worker models execute in parallel. Learnings persist in local, per-project memory.
amplify → spec → scope → dispatch → audit → deploy
Start anywhere. Auto-advance forward. Memory persists across sessions.
Providers ·
Skills (27)

amplify SKILL.md View full skill →
Use when a prompt is rough, vague, or under-specified and you want it rewritten to high quality before running it.
ReadGlobGrepAgentAskUserQuestionSkill
Amplify

Turn a rough prompt into a high-signal one. Detect the domain, inject the standards that domain demands, score it against a rubric — then offer to run it.
Dispatcher and reviewer — Opus 4.8 (thinking-tier). Searcher/Writer — Sonnet 4.6 (worker-tier).
Amplify does one thing well: it rewrites the prompt you give it into the single strongest version, then hands it off. It does not write code itself — it produces a prompt other skills (or you) execute.
Per-Step Agent Map (DOCTRINE rule 12)

Every substantive step dispatches at least one Agent. Atomic steps (DOCTRINE 12.2.8) are a single Worker → Reviewer pair with no independent angles to fan out.
Step	Status	Worker tier	Thinking tier	Notes
1 — Read intent	Atomic (12.2.8)	Searcher (Sonnet) — domain signals + project rules	Analyst (Opus) — triage + gap analysis + persona selection	Single Worker → Reviewer; reads `CLAUDE.md`, `AGENTS.md`, `.hyperflow/memory/*`
2 — Amplify	Atomic (12.2.8)	Writer (Sonnet) — draft the enhanced prompt	Reviewer (Opus) — rubric score, one targeted revision	Writer drafts → Opus scores against the 8-dim rubric → revise once if any dim < 4
3 — Present + handoff	§12.1 inline	—	—	Print the amplified prompt + rationale; fire the handoff gate (`AskUserQuestion`)
Inputs

$ARGUMENTS — the raw prompt to amplify. If empty, amplify the user's previous message in the conversation.
No flags. Amplify always produces the single best version (per the design decision); the rubric, not a flag, governs depth.
Flow

Step 1 — Read intent (atomic · 12.2.8)

Atomic — a single Searcher → Analyst pair. No parallel angles: understanding one prompt is one scope.
Dispatch Searcher — detecting prompt domain + gathering project rules (Sonnet). It returns:
Domain signals — does the prompt concern frontend/ui/creative, api/db backend, mobile, security, performance, refactor/bugfix/test, devops, docs? (A prompt can span several.)
Project rules — read, when present: CLAUDE.md, AGENTS.md, .hyperflow/memory/conventions.md, .hyperflow/memory/project-decisions.md, .hyperflow/memory/anti-patterns.md. Extract any rule that should constrain the prompt.
The raw prompt's gaps — what a senior engineer would have to guess to act on it.
Dispatch Analyst — triaging intent + selecting personas (Opus). It returns {

                
                  
                  
                  audit
                  SKILL.md
                  View full skill →
                
                
                  Use when the user wants a code review on recent changes — quality, spec, security, or performance feedback.
                  
                      ReadBash(git:*)GlobGrepAgentAskUserQuestion
                    
                
                
                  Audit
Multi-level code review. Dispatcher — Opus 4.8 (thinking-tier). Workers — Sonnet 4.6.
This skill exercises Layer 3 (Orchestrator) and Layer 9 (Security). After the review prints, a fix gate asks the user whether to apply the findings — on Yes, audit auto-invokes /hyperflow:scope with the findings as the spec, which then chains to /hyperflow:dispatch.
Iron Rules
Failure recovery (DOCTRINE rule 14). Worker errors, malformed output, NEEDS_REVISION verdicts, and gate failures in every Step follow the canonical policy in skills/hyperflow/failure-recovery.md. Audit-specific exception: a failed Reviewer at L1/L2 escalates to an L3+ Reviewer at the same severity level rather than aborting — audit exists to catch issues, so a Reviewer failure is best resolved by a more thorough Reviewer, not by stopping the chain.
Per-Step Agent Map (DOCTRINE rule 12)

                
                  
                  
                  background
                  SKILL.md
                  View full skill →
                
                
                  Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs.
                  
                      ReadWriteEditBash(ls:*)Bash(cat:*)Bash(rm:*)Bash(find:*)GlobGrep
                    
                
                
                  Background
Read-only-by-default management interface for background agents fired by other hyperflow skills (dispatch quality gates, deploy CI watcher, scaffold analysis refresh, cache compact, scope speculative prefetch). Reads from .hyperflow/background/registry.json + per-agent output buffers.
Full doctrine: background-agents.md.
Subcommands

Step
Sub-phase
Worker tier
Thinking tier
Notes


1 — Resolve scope
—
—
—
Mechanical decision (exempt)


2 — Gather context
2a — Surface mapping
Searcher × 2 (glob + import-graph)
Sonnet Reviewer
Parallel


2 — Gather context
2b — Semantic indexing
Searcher × 2 (type-system + symbol-graph)
Sonnet Reviewer
Parallel


2 — Gather context
2c — Convention scan
Searcher × 1 (test patterns + lint config)
Sonnet Reviewer
Justified single-angle


2 — Gather context
2d — Aggregate coverage gate
—
Reviewer (Opus) verifies aggregate coverage
Thinking-tier coverage gate


3 — Review
3a — L1+L2 (syntax/format/naming)
—
Reviewer (Opus) × 2 (different file groups) + Sonnet Reviewer aggregates verdicts
Parallel Opus pair; justified single-tier (Opus are the workers at L1-L2)


3 — Review
3b — L3 (integration/security)
—
Reviewer (Opus) × 2 (integration + security) + Sonnet Reviewer aggregates verdicts
Parallel Opus pair; justified single-tier (L3 requires thinking-tier)


3 — Review
3c — L4+L5 (perf/scale/a11y/UX)
—
Reviewer (Opus) × 2 (perf/scale + a11y/UX) + Sonnet Reviewer aggregates verdicts
Parallel Opus pair; justified single-tier (L4-L5 requires thinking-tier)


4 — Findings synthesis
4a — Critical findings
Writer × 2 (evidence probe + impact analysis)
Sonnet Reviewer
Parallel

                
              

Subcommand
Description


list
Print the registry: in-flight · completed-uncollected · stalled · errored


show 
Print one agent's output buffer (.hyperflow/background/.md)


cancel 
Cancel one specific in-flight agent


cancel --all
Cancel every in-flight agent (use before closing a session)


prune
Delete completed .hyperflow/background/.md files older than 7 days


Default subcommand when none provided: list.
Subcommand Details
list
Read .hyperflow/background/registry.json. Group entries by status and print a compact table:

## In flight (N)

| ID                                | Purpose                              | Fired      | Timeout | Blocks  |
|-----------------------------------|--------------------------------------|------------|---------|---------|
| `bg-1718049600-quality-gates-b2`  | Layer 5 gates Batch 2                | 17:30      | 18:00   | step3   |
| `bg-1718049820-ci-watcher`        | GitHub Actions watch for v4.7.0      | 17:33      | 18:33   | —       |

## Completed (uncollected, N)

| ID                                | Purpose                              | Completed  | Duration | Output |
|-----------------------------------|--------------------------------------|------------|----------|--------|
| `bg-1718045400-scaffold-refresh`  | Refresh .hyperflow/architecture.md   | 16:42      | 2m 18s   | 1.4kb  |

## Stalled / Errored (N)

| ID                                | Purpose                              | Status            | Reason            |
|-----------------------------------|--------------------------------------|-------------------|-------------------|
| `bg-1717980000-cache-compact`     | Compact learnings.md                 | STALLED           | timeout (30m)     |

Print one trailing line:  in flight ·  uncollected ·  needs attention. If registry is empty, print No background agents. and stop.
show 
Read .hyperflow/background/.md and print it verbatim. If the agent is still running, print the registry entry first then Output buffer not yet written.
                

              

                
                  
                  
                  bridge
                  SKILL.md
                  View full skill →
                
                
                  Use when the user wants hyperflow's behavioral rules to apply outside the terminal CLI — in Claude Code Desktop, claude.
                  
                      ReadWriteEditBash(cat:*)Bash(ls:*)Bash(date:*)
                    
                
                
                  Bridge
Embed the portable subset of hyperflow's doctrine into the project's CLAUDE.md so it applies in surfaces that don't load CLI plugins (Claude Code Desktop, claude.ai web, IDE extensions). The doctrine block is managed via fenced markers, so refreshing it on plugin updates is idempotent and never touches your own CLAUDE.md content.
Source template: templates/claude-md-doctrine.md. Doctrine background: DOCTRINE.md.
Subcommands

Subcommand
Description


generate
Write the doctrine block into the project's CLAUDE.md (create the file if absent, append the block if not present, refresh if already present)


refresh
Same as generate — alias for clarity when the block already exists


remove
Remove the doctrine block from CLAUDE.md (preserves your own content; if the file becomes empty after removal, leave it as an empty file rather than delete)


status
Show whether the doctrine block is present, its version, when it was generated


`mode 
manual\
off>`
Set the auto-bridge mode for this project. Writes .hyperflow/.bridge-mode. The session-start hook reads this and decides what to do


Default subcommand when none provided: status.
Auto-bridge (default ON)
The CLI session-start hook (hooks/session-start) runs scripts/auto-bridge.py on every session start. Behavior depends on the mode stored in .hyperflow/.bridge-mode:

Mode
Behavior


auto (default when .bridge-mode is absent)
If ./CLAUDE.md is missing the doctrine block OR has an outdated version, silently writes/refreshes the block and prints a one-line notice in session-start output. Zero user friction.


manual
Never writes. Prints a one-line advisory when the block is missing or outdated: ./CLAUDE.md doctrine block would be refreshed (version 4.11.0) — run /hyperflow:bridge refresh to apply.


off
Does nothing. No writes, no advisories.


This means: open Claude Code CLI once in your project, and from then on every Desktop / web / IDE session in the same project automatically gets the up-to-date hyperflow doctrine via CLAUDE.md. Refresh on plugin update is automatic too.
To opt out: /hyperflow:bridge mode off. To require explicit refresh
                
              

                
                  
                  
                  cache
                  SKILL.md
                  View full skill →
                
                
                  Use when the user wants to view, search, add, edit, prune, archive, or clear hyperflow memory entries.
                  
                      ReadWriteEditBash(ls:*)Bash(mv:*)Bash(rm:*)GlobGrep
                    
                
                
                  Cache
CRUD interface for .hyperflow/memory/. Full protocol: memory-system.md.
Storage
All operations target .hyperflow/memory/ at the project root. Never modify source code files — if asked to "remember X about file Y", add a memory entry only, never edit Y.
Subcommands

Subcommand
Description


show [tag]
Print index or filter entries by tag


search 
Full-text search across all memory files


add  </code></td>
<td>Append a new entry (prompts for details)</td>
</tr>
<tr>
<td><code>edit <entry-id></code></td>
<td>Find entry by date+title slug and update in place</td>
</tr>
<tr>
<td><code>prune</code></td>
<td>Remove stale, superseded, and orphaned entries</td>
</tr>
<tr>
<td><code>archive</code></td>
<td>Move entries older than 30 days to cold storage</td>
</tr>
<tr>
<td><code>clear</code></td>
<td>Wipe all memory (with confirmation, recoverable)</td>
</tr>
<tr>
<td><code>stats</code></td>
<td>Counts, tier breakdown, tag frequency, oldest/newest</td>
</tr>
<tr>
<td><code>migrate</code></td>
<td>Import entries from legacy <code>~/.claude/hyperflow-memory.md</code></td>
</tr>
<tr>
<td><code>off</code></td>
<td>Disable memory writes for this session</td>
</tr>
<tr>
<td><code>compact</code></td>
<td>Summarise aged memory entries into stubs + monthly archive sidecars</td>
</tr>
</tbody></table>
<h2>Subcommand Details</h2>
<h3><code>show [tag]</code></h3>
<p>No arg → print <code>index.md</code>. With tag → filter all files for matching entries.</p>
<p>Output table: <code>Date | Title | Tags | File | Tier</code></p>
<h3><code>search <query></code></h3>
<p>grep/ripgrep across <code>learnings.md</code>, <code>decisions.md</code>, <code>pitfalls.md</code>, <code>patterns.md</code>, <code>conventions.md</code>.</p>
<p>Return <code>file:line</code> + snippet, ranked by relevance.</p>
<h3><code>add <category> <title></code></h3>
<p>Categories: <code>learning</code> <code>decision</code> <code>pitfall</code> <code>pattern</code> <code>convention</code></p>
<p>Prompt via AskUserQuestion for: <code>what</code>, <code>why it matters</code>, <code>tags</code> (controlled vocab).</p>
<p>Append to the matching file using:</p>
<pre><code>
### [YYYY-MM-DD] <title>  `[tag1, tag2]`
**What:** ...
**Why it matters:** ...
**Evidence:** ...
</code></pre>
<p>Update <code>index.md</code> with the new row.</p>
<h3><code>edit <entry-id></code></h3>
<p>Locate by date+title slug. Show current value, prompt for new value, update in place.</p>
<h3><code>prune</code></h3>
<p>Per <a href="references/memory-system.md">memory-system.md</a> pruning protocol:</p>
<ul>
<li>Remove <code>[SUPERSEDED]</code> entries older than 7 days</li>
<li>Remove entries whose referenced files no longer exist (<code>test </div>
                </div>
              </div><div class="gist-card" data-skill-slug="deploy" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>deploy</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/deploy/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes.</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Write</span><span class="tool-pill" data-astro-cid-vaomz7ca>Edit</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(git:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(npm:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(pnpm:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(./scripts/*:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Glob</span><span class="tool-pill" data-astro-cid-vaomz7ca>Grep</span><span class="tool-pill" data-astro-cid-vaomz7ca>AskUserQuestion</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Deploy</h1>
<p>No gate skipped, no failure ignored. If any gate fails, halt and report. Never <code>--no-verify</code>. Never bypass.</p>
<p><strong>Failure recovery (rule 14).</strong> Worker errors and Quality Gate failures follow the canonical policy in <a href="../hyperflow/failure-recovery.md"><code>skills/hyperflow/failure-recovery.md</code></a>. Gate failures are user-surfaced, never auto-fixed — print the failing command + full stderr and halt the push. Never <code>--no-verify</code>, never force-push to main.</p>
<h2>Per-Step Agent Map</h2>
<table><thead><tr>
<th>Step</th>
<th>Sub-phase</th>
<th>Worker tier</th>
<th>Thinking tier</th>
<th>Notes</th>
</tr></thead><tbody>
<tr>
<td>1a</td>
<td>Repo-state scan</td>
<td>Worker A (git status), Worker B (git log)</td>
<td>Sonnet</td>
<td>—</td>
</tr>
<tr>
<td>1b</td>
<td>Tool detection</td>
<td>Worker A (profile.md + lockfiles), Worker B (testing.md + devDeps)</td>
<td>Sonnet</td>
<td>—</td>
</tr>
<tr>
<td>2a</td>
<td>Lint + typecheck (parallel)</td>
<td>Worker A (linter), Worker B (formatter), Worker C (tsc)</td>
<td>Sonnet</td>
<td>Step 3 (Security Sweep) runs in parallel with Step 2 at orchestrator level; 2a halts chain on any failure before 2b</td>
</tr>
<tr>
<td>2b</td>
<td>Build gate</td>
<td>Worker A (prod build), Worker B (dev build)</td>
<td>Sonnet</td>
<td>Depends on 2a PASS</td>
</tr>
<tr>
<td>2c</td>
<td>Test gate</td>
<td>Worker A (unit), Worker B (integration/E2E)</td>
<td>Sonnet</td>
<td>Parallel (P1); depends on 2b PASS</td>
</tr>
<tr>
<td>3a</td>
<td>Secrets scan</td>
<td>Worker A (diff pattern), Worker B (file pattern)</td>
<td><strong>Opus</strong></td>
<td>Runs in parallel with Step 2 (pre-build; read-only)</td>
</tr>
<tr>
<td>3b</td>
<td>Dependency audit</td>
<td>Worker A (CVE audit), Worker B (license check)</td>
<td>Sonnet</td>
<td>—</td>
</tr>
<tr>
<td>4</td>
<td>Commit</td>
<td>single Worker</td>
<td>Sonnet</td>
<td>atomic-exempt (DOCTRINE 12.2)</td>
</tr>
<tr>
<td>5a</td>
<td>Release execution</td>
<td>single Worker</td>
<td>Sonnet</td>
<td>atomic-exempt (DOCTRINE 12.2)</td>
</tr>
<tr>
<td>5b</td>
<td>Version sync</td>
<td>Worker A (manifests), Worker B (changelog)</td>
<td>Sonnet</td>
<td>—</td>
</tr>
<tr>
<td>6</td>
<td>Push gate</td>
<td>AskUserQuestion</td>
<td>—</td>
<td>structural gate; atomic-exempt</td>
</tr>
<tr>
<td>7</td>
<td>Output</td>
<td>single print</td>
<td>—</td>
<td>atomic-exempt (§12.1)</td>
</tr>
</tbody></table>
<h2>Step 1 — Survey State</h2>
<p>Sub-phases run in parallel (P1).</p>
<h3>Step 1a — Repo-state scan</h3>
<p>Two Workers in parallel:</p>
<ul>
<li>Worker A — <code>git status --short</code> — uncommitted changes, staged files</li>
<li>Worker B — <code>git log origin/<branch>..HEAD --oneline</code> — commits ahead of remote; detect branch name</li>
</ul>
<p>Sonnet Reviewer — verdict on repo state (clean / has uncommitted / ahead by N). If detached HEAD or no remote configured → halt with reason.</p>
<h3>Step 1b — Tool detection</h3>
<p></div>
                </div>
              </div><div class="gist-card" data-skill-slug="dispatch" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>dispatch</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/dispatch/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when a task file exists in .</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Write</span><span class="tool-pill" data-astro-cid-vaomz7ca>Edit</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(git:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Agent</span><span class="tool-pill" data-astro-cid-vaomz7ca>AskUserQuestion</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Dispatch</h1>
<p>Workhorse phase. Picks up a task file from <code>/hyperflow:scope</code> and runs it through the orchestrator pattern with parallel worker dispatch and thinking-tier reviews.</p>
<p>This skill exercises <strong>Layer 3 (Orchestrator)</strong>, <strong>Layer 5 (Quality Gates)</strong>, <strong>Layer 6 (Project Memory)</strong>, <strong>Layer 8 (Git Workflow)</strong>, and <strong>Layer 9 (Security)</strong> from the doctrine. Multi-level review (L1–L5) is applied per the triage's flow profile.</p>
<h2>Per-Step Agent Map (DOCTRINE rule 12 — §12.1 inline-allowed for trivial steps · §12.2 sub-phase decomposition)</h2>
<p>Every substantive step dispatches at least one Agent. Trivial steps (≤ 2 tool calls, no content generation, no decision-making, mechanically verifiable) MAY be performed inline by the orchestrator per §12.1. Non-trivial steps decompose into ≥ 2 named sub-phases per §12.2.</p>
<table><thead><tr>
<th>Step</th>
<th>Sub-phase</th>
<th>Worker tier</th>
<th>Thinking tier</th>
<th>Notes</th>
</tr></thead><tbody>
<tr>
<td>0 — Mode confirm</td>
<td>— (exempt)</td>
<td>—</td>
<td>—</td>
<td><code>AskUserQuestion</code> only</td>
</tr>
<tr>
<td>0.5 — Operational choices</td>
<td>— (exempt)</td>
<td>—</td>
<td>—</td>
<td><code>AskUserQuestion</code> only</td>
</tr>
<tr>
<td>1 — Load task</td>
<td>— (atomic · §12.2.8)</td>
<td>—</td>
<td>—</td>
<td>Read + schema check = single mechanical decision; no parallel angles</td>
</tr>
<tr>
<td>2a — Pre-dispatch</td>
<td>Composer × N parallel (Sonnet) — one per sub-task; stitches persona + injects learnings</td>
<td><strong>Reviewer</strong> (Sonnet) — reviews prompt set for completeness</td>
<td>Parallel worker prompts built before any fan-out fires</td>
</tr>
<tr>
<td>2b — Worker fan-out</td>
<td>Implementer / Searcher / Writer × N parallel (Sonnet)</td>
<td><strong>Reviewer</strong> (Sonnet · worker tier) — batched over full batch (P2) or per-sub-task fallback (mixed caps / <code>--thorough</code>)</td>
<td>One Reviewer call per batch · escalates to Opus under <code>--thorough</code></td>
</tr>
<tr>
<td>2c — Gate run</td>
<td>Worker (Sonnet) — runs lint/typecheck/tests on affected files</td>
<td><strong>Reviewer</strong> (Sonnet) — judges gate output</td>
<td>Small focused diff; Sonnet sufficient</td>
</tr>
<tr>
<td>2d — Learnings + commit</td>
<td>Writer (Sonnet) — synthesizes per-batch learnings</td>
<td>— (mechanical commit · §12.1)</td>
<td>Per-sub-task PASS commits land here; learnings appended to context</td>
</tr>
<tr>
<td>3 — Final integration review</td>
<td>— (atomic · §12.2.8)</td>
<td><strong>Reviewer</strong> (Opus · thinking tier) — L1–L<n> over full diff</td>
<td>Single Reviewer dispatch, no parallel angles; atomic-exempt</td>
</tr>
<tr>
<td>4 — Wrap up</td>
<td>Writer (Sonnet) — optional; only if memory prose is non-trivial</td>
<td>—</td>
<td>§12.1 trivial-inline; no Reviewer (D5)</td>
</tr>
<tr>
<td>5 — End of chain</td>
<td>— (exempt)</td>
<td>—</td>
<td>ONE <cod</div>
                </div>
              </div><div class="gist-card" data-skill-slug="flush" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>flush</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/flush/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when the user wants to manually flush a deferred-commit queue from a prior or interrupted chain.</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(git:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(ls:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(cat:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(rm:*)</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Flush</h1>
<p>Manually flush the deferred-commit queue from a chain that ran with <code>commit-when=end</code>. Normally <code>/hyperflow:dispatch</code> calls <code>scripts/flush-commits.sh</code> at its Step 4 wrap-up; this skill exists for the case where the chain was interrupted (crash, kill, context loss) before the auto-flush ran.</p>
<h2>Subcommands</h2>
<table><thead><tr>
<th>Subcommand</th>
<th>Description</th>
</tr></thead><tbody>
<tr>
<td>(no arg)</td>
<td>Run <code>scripts/flush-commits.sh <project-root></code> — fast-forward staging onto user's branch, delete staging, clear queue</td>
</tr>
<tr>
<td><code>--dry-run</code></td>
<td>Show what would be flushed without doing it. Lists the queued commits in order.</td>
</tr>
</tbody></table>
<h2>What gets flushed</h2>
<p><code>.hyperflow/commits-queue/manifest.json</code> tracks the chain's <code>user<em>branch</code>, <code>staging</em>branch</code> (always <code>hyperflow/staging-<chain-id></code>), and the list of queued commits with SHAs and messages. Flush replays them via <code>git merge --ff-only</code> so:</p>
<ul>
<li>All N commits land on the user's branch with original SHAs preserved</li>
<li>Order is chronological (queue-time order)</li>
<li>Original commit messages are preserved</li>
<li>Original file-to-message mapping is preserved (each commit touched exactly the files its sub-task touched)</li>
</ul>
<h2>What happens if fast-forward isn't possible</h2>
<p>If the user's branch diverged from staging (e.g. the user committed manually mid-chain on the same branch), <code>git merge --ff-only</code> refuses. The skill surfaces the error with two recovery options:</p>
<ol>
<li><code>git rebase hyperflow/staging-<chain-id></code> — replay staging commits on top of user's new commits</li>
<li><code>git cherry-pick <staging-base>..hyperflow/staging-<chain-id></code> — selectively pick commits</li>
</ol>
<p>The staging branch is preserved for the user to act on manually. The queue manifest stays in place so a future <code>/hyperflow:flush</code> retry can attempt again after the user resolves divergence.</p>
<h2>Flow</h2>
<ol>
<li>Check <code>.hyperflow/commits-queue/manifest.json</code> exists. If not, print <code>No queue to flush.</code> and stop.</li>
<li>Run <code>bash $PLUGIN<em>ROOT/scripts/flush-commits.sh $PROJECT</em>ROOT [--dry-run]</code>.</li>
<li>Print the script's output verbatim.</li>
</ol>
<h2>Overview</h2>
<p><code>/hyperflow:flush</code> is the user-facing handle for the deferred-commit flush mechanism. Most users never call it explicitly — <code>/hyperflow:dispatch</code> Step 4 wrap-up runs the same script automatically. This skill exists for recovery: if a chain ran with <code>commit-when=end</code> and crashed before wrap-up, the queue persists on disk and the user can flush it later.</p>
<h2>Prerequisites</h2>
<ul>
<li><code>.hyperflow/commits-queue/manifest.json</code> exists from a prior chain run with <code>commit-when=end</code>.</li>
<li>Git repositor</div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>"Use when applying Hyperflow's orchestration doctrine in Codex, Antigravity, or another single-agent surface.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Hyperflow Doctrine (single-agent port)</h1>
<p>Apply Hyperflow's behavioral floor in surfaces that load skills but do not provide the full Claude Code multi-agent runtime.</p>
<h2>Runtime Adaptation</h2>
<p>Codex and Antigravity run one foreground agent. Where the full doctrine says to dispatch parallel workers under reviewers:</p>
<ul>
<li>Do the work yourself, one coherent batch at a time.</li>
<li>Self-review each batch before moving on.</li>
<li>Run a final integration self-review over the cumulative diff.</li>
<li>Preserve the same autonomy, clarification, commit cadence, file-first artefact, no-attribution, and security rules.</li>
</ul>
<h2>Codex Function Router</h2>
<p>Codex loads Hyperflow as skills, not as native Claude-style slash commands. Treat these user messages as function aliases and execute the matching skill workflow inline in the current thread:</p>
<table><thead><tr>
<th>User says</th>
<th>Run</th>
</tr></thead><tbody>
<tr>
<td><code>/hyperflow:amplify</code>, <code>hyperflow amplify</code>, <code>use hyperflow amplify</code></td>
<td><code>amplify</code></td>
</tr>
<tr>
<td><code>/hyperflow:spec</code>, <code>hyperflow spec</code>, <code>design with hyperflow</code></td>
<td><code>spec</code></td>
</tr>
<tr>
<td><code>/hyperflow:scope</code>, <code>hyperflow scope</code>, <code>decompose with hyperflow</code></td>
<td><code>scope</code></td>
</tr>
<tr>
<td><code>/hyperflow:dispatch</code>, <code>hyperflow dispatch</code>, <code>run the hyperflow plan</code></td>
<td><code>dispatch</code></td>
</tr>
<tr>
<td><code>/hyperflow:workflow</code>, <code>hyperflow workflow</code>, <code>run a workflow</code></td>
<td><code>workflow</code></td>
</tr>
<tr>
<td><code>/hyperflow:trace</code>, <code>hyperflow trace</code>, <code>debug with hyperflow</code></td>
<td><code>trace</code></td>
</tr>
<tr>
<td><code>/hyperflow:audit</code>, <code>hyperflow audit</code>, <code>review with hyperflow</code></td>
<td><code>audit</code></td>
</tr>
<tr>
<td><code>/hyperflow:deploy</code>, <code>hyperflow deploy</code>, <code>ship with hyperflow</code></td>
<td><code>deploy</code></td>
</tr>
<tr>
<td><code>/hyperflow:cache</code>, <code>hyperflow cache</code></td>
<td><code>cache</code></td>
</tr>
<tr>
<td><code>/hyperflow:status</code>, <code>hyperflow status</code></td>
<td><code>status</code></td>
</tr>
<tr>
<td><code>/hyperflow:sticky</code>, <code>hyperflow sticky</code></td>
<td><code>sticky</code></td>
</tr>
<tr>
<td><code>/hyperflow:bridge</code>, <code>hyperflow bridge</code></td>
<td><code>bridge</code></td>
</tr>
<tr>
<td><code>/hyperflow:flush</code>, <code>hyperflow flush</code></td>
<td><code>flush</code></td>
</tr>
<tr>
<td><code>/hyperflow:background</code>, <code>hyperflow background</code></td>
<td><code>background</code></td>
</tr>
<tr>
<td><code>/hyperflow:scaffold</code>, <code>hyperflow scaffold</code></td>
<td><code>scaffold</code></td>
</tr>
</tbody></table>
<p>Do not answer that <code>/hyperflow:*</code> is an unknown comm</div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-amplify" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-amplify</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-amplify/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow prompt amplifier.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-amplify — prompt amplifier (Antigravity single-agent)</h1>
<p>Turn a rough prompt into the single strongest version, then hand it off. <strong>Amplify never writes code</strong> — it produces a prompt other workflows (or you) execute. Follow the <code>hyperflow</code> doctrine.</p>
<h2>Steps</h2>
<ol>
<li><strong>Read intent.</strong> Detect the prompt's domain(s) (frontend/ui, api/db backend, mobile, security, performance, refactor/bugfix/test, devops, docs). Read project rules when present: <code>AGENTS.md</code>, <code>~/.gemini/AGENTS.md</code>, <code>.hyperflow/memory/*</code>. Note the gaps a senior engineer would have to guess.</li>
<li><strong>Amplify.</strong> Rewrite into the single strongest version using this skeleton (adapt section presence — economy is a constraint, never inflate a one-liner into a spec):</li>
</ol>
<ul>
<li>role / expertise framing (one line)</li>
<li>precise task (unambiguous goal)</li>
<li>Context (relevant background, current state, inputs)</li>
<li>Constraints (domain doctrine standards + project rules — project rules win on conflict)</li>
<li>Output (deliverable format + acceptance criteria)</li>
<li>Out of scope (explicit anti-goals)</li>
</ul>
<ol>
<li><strong>Score</strong> the draft against the 8-dimension rubric (1-5 each): intent clarity · context sufficiency · scope boundaries · structure · domain doctrine injected · output spec · guardrails · economy. If any dimension < 4, revise once.</li>
<li><strong>Present</strong> the amplified prompt in one copy-ready fenced block + a 2-4 line rationale (what changed, which standards/project rules were injected, any flagged ambiguity).</li>
<li><strong>Handoff gate</strong> (AskUserQuestion, 4 options → mark one Recommended): Send to <code>hyperflow-spec</code> (Recommended) · Send to <code>hyperflow-scope</code> · Send to <code>hyperflow-dispatch</code> · Copy only. On a "Send to…" choice, invoke that workflow with the amplified prompt.</li>
</ol>
<h2>Rules</h2>
<ul>
<li>Never write code. Project rules override generic persona standards. No AI attribution in the amplified prompt or rationale.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-audit" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-audit</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-audit/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow code review.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-audit — review phase (Antigravity single-agent)</h1>
<p>Multi-level review over a target (default: <code>git diff HEAD</code> + staged). Follow the <code>hyperflow</code> doctrine. Security scan is mandatory at L3+.</p>
<h2>Levels</h2>
<table><thead><tr>
<th>L</th>
<th>Checks</th>
</tr></thead><tbody>
<tr>
<td>1</td>
<td>syntax, obvious bugs, formatting</td>
</tr>
<tr>
<td>2</td>
<td>L1 + spec compliance, naming, edge cases</td>
</tr>
<tr>
<td>3</td>
<td>L2 + cross-file consistency, integration risks, security (secrets, injection, path traversal, XSS, missing validation)</td>
</tr>
<tr>
<td>4</td>
<td>L3 + architecture, scalability, accessibility</td>
</tr>
<tr>
<td>5</td>
<td>L4 + adversarial probing, perf profiling, alternatives</td>
</tr>
</tbody></table>
<p>Default to L2; elevate to L3 when the diff touches auth, data, money, or external input.</p>
<h2>Steps</h2>
<ol>
<li><strong>Resolve scope</strong> (target arg or current diff). Read the changed files + their immediate dependencies.</li>
<li><strong>Review</strong> at the chosen level. Grade each finding <code>[Critical] / [Important] / [Suggestion] / [Praise]</code> with <code>file:line</code> + a concrete fix.</li>
<li><strong>Write</strong> the full report to <code>.hyperflow/audits/<YYYY-MM-DD-HHmm>-<scope>.md</code> (status table → TL;DR → findings → security-scan table). Print a one-line summary pointing at the file.</li>
<li><strong>Fix gate</strong> via AskUserQuestion (only when Critical/Important exist): <code>Fix all (Recommended) / Critical+Important / Critical only / No</code>. On a fix choice, route the findings into <code>hyperflow-scope</code> → <code>hyperflow-dispatch</code>. On <code>SECURITY_VIOLATION</code>, skip the gate and surface immediately.</li>
</ol>
<h2>Rules</h2>
<ul>
<li>Findings live in the file, not chat — chat shows only the summary box.</li>
<li>A clean run (no Critical/Important) prints <code>Audit clean</code> and still writes the file for history.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-cache" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-cache</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-cache/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow memory manager.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-cache — memory CRUD (Antigravity single-agent)</h1>
<p>Manage <code>.hyperflow/memory/</code> entries. <strong>Only memory files</strong> — never source code. Follow the <code>hyperflow</code> doctrine.</p>
<h2>Operations</h2>
<ul>
<li><strong>view / list</strong> — print the entries in <code>.hyperflow/memory/{decisions,learnings,pitfalls,patterns}.md</code>.</li>
<li><strong>search <code><term></code></strong> — grep the memory files; show matching entries with their file + heading.</li>
<li><strong>add</strong> — append a tagged entry to the right category file (decisions / learnings / pitfalls / patterns). Use the format: <code>## <topic></code> then <code>- <fact> (recorded <YYYY-MM-DD>)</code>.</li>
<li><strong>edit <code><entry></code></strong> — update an existing entry in place (don't duplicate).</li>
<li><strong>prune / clear</strong> — remove stale or wrong entries. Confirm via AskUserQuestion before a destructive clear (binary Yes/No).</li>
</ul>
<h2>Rules</h2>
<ul>
<li>Scope is <code>.hyperflow/memory/</code> only. Don't record what the repo/git already captures; record the non-obvious why.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-deploy" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-deploy</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-deploy/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow ship phase.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-deploy — ship phase (Antigravity single-agent)</h1>
<p>Gate, then ship. Follow the <code>hyperflow</code> doctrine. Pushing is always an explicit, confirmed step.</p>
<h2>Steps</h2>
<ol>
<li><strong>Pre-push gates</strong> — run in order, fix or halt on failure:</li>
</ol>
<ul>
<li>lint · typecheck · build · tests · a quick security sweep (no secrets in the diff, no blocked files committed).</li>
</ul>
<ol>
<li><strong>Report</strong> the gate results in one short block (pass/fail per gate).</li>
<li><strong>Push gate</strong> via AskUserQuestion — binary <code>Push / Hold</code> (no recommended marker). State the branch, ahead/behind vs the remote, and any caveat (e.g. red gate from someone else's files).</li>
<li>On <strong>Push</strong>: <code>git push</code> the branch (never <code>--force</code> to <code>main</code>/<code>master</code>). On <strong>Hold</strong>: leave commits local and say so.</li>
</ol>
<h2>Hard rules</h2>
<ul>
<li><strong>Never</strong> <code>git push --no-verify</code>. If a pre-push hook fails — even on files you don't own — surface it and hold; do not bypass.</li>
<li><strong>Never</strong> force-push to <code>main</code>/<code>master</code>.</li>
<li>If a gate is red because of a concurrent session's uncommitted/untracked files, report that the push is held on external failure — your commits stay clean and local until the tree is green.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-dispatch" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-dispatch</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-dispatch/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow execution phase.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-dispatch — execution phase (Antigravity single-agent)</h1>
<p>Execute the task file from <code>hyperflow-scope</code>. <strong>No sub-agent dispatch and no model tiers in Antigravity</strong> — you do each batch yourself, then self-review before committing. Follow the <code>hyperflow</code> doctrine.</p>
<h2>Per batch</h2>
<ol>
<li><strong>Implement</strong> every sub-task in the batch (sequentially; they were planned as small, independent units).</li>
<li><strong>Self-review</strong> the batch diff against the level checklist:</li>
</ol>
<ul>
<li><strong>L1</strong> syntax/format/obvious bugs · <strong>L2</strong> spec compliance, naming, edge cases · <strong>L3</strong> cross-file integration + security (secrets, injection, validation).</li>
<li>Elevate to L3 when the change touches auth, data, or external input. Fix anything found before committing.</li>
</ul>
<ol>
<li><strong>Quality gates</strong> on affected files: run the project's lint, typecheck, and tests. Fix failures (never <code>--no-verify</code>).</li>
<li><strong>Commit per sub-task</strong> — one sub-task = one conventional commit (respect commitlint: lowercase subject, allowed scope). Stage only that sub-task's files; never commit files you didn't change.</li>
<li><strong>Update the task file's status block</strong> (tick the sub-task, bump progress) and append any durable learning to <code>.hyperflow/memory/</code>.</li>
</ol>
<h2>After all batches</h2>
<ol>
<li><strong>Final integration self-review</strong> over the cumulative diff — catch cross-batch contradictions, scope leaks, and <code>any</code>/type regressions.</li>
<li><strong>End gate</strong> via AskUserQuestion: offer to run <code>hyperflow-audit</code> (independent review) and/or <code>hyperflow-deploy</code>. Both are binary (no recommended marker). Never auto-push.</li>
</ol>
<h2>Rules</h2>
<ul>
<li>A <code>SECURITY_VIOLATION</code> halts immediately — no commit, no continue.</li>
<li>If the working tree is dirty with files you didn't create (concurrent work), never stage them; re-check <code>git status</code> before each commit.</li>
<li>Auto mode completes every sub-task before any summary — no partial "to resume" hand-offs.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-scaffold" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-scaffold</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-scaffold/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow project setup.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-scaffold — project setup (Antigravity single-agent)</h1>
<p>One-shot setup of hyperflow's project surfaces. Follow the <code>hyperflow</code> doctrine.</p>
<h2>Steps</h2>
<ol>
<li><strong>Create the <code>.hyperflow/</code> cache</strong> at the repo root if absent:</li>
</ol>
<ul>
<li><code>.hyperflow/memory/</code> with <code>decisions.md</code>, <code>learnings.md</code>, <code>pitfalls.md</code>, <code>patterns.md</code> (empty stubs, each with a one-line header).</li>
<li><code>.hyperflow/tasks/</code>, <code>.hyperflow/specs/</code>, <code>.hyperflow/audits/</code> (empty dirs).</li>
</ul>
<ol>
<li><strong>Write context files</strong> (<code>.hyperflow/profile.md</code>, <code>architecture.md</code>, <code>conventions.md</code>) by reading the repo: stack, top-level layout, test/lint conventions, commit conventions. Keep each short and factual.</li>
<li><strong>Install project slash commands</strong>: copy the seven <code>hyperflow*</code> workflow files into <code><repo>/.agent/workflows/</code> (so <code>/hyperflow</code>, <code>/hyperflow-spec</code>, … resolve in Antigravity's <code>/</code> menu). Source: the <code>templates/antigravity/workflows/</code> shipped with hyperflow.</li>
<li><strong>Note</strong> that global hyperflow skills live in <code>~/.gemini/config/skills/</code> (auto-trigger) and global rules in <code>~/.gemini/AGENTS.md</code>.</li>
<li>Print a one-line summary of what was created. Do NOT start the chain.</li>
</ol>
<h2>Rules</h2>
<ul>
<li>Idempotent — never clobber existing <code>.hyperflow/</code> content; only create what's missing.</li>
<li><code>.hyperflow/tasks</code> and <code>.hyperflow/specs</code> are runtime artefacts; <code>.hyperflow/memory</code> is durable and worth committing.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-scope" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-scope</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-scope/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow planning phase.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-scope — decomposition phase (Antigravity single-agent)</h1>
<p>Decompose, don't build. The only writes are to <code>.hyperflow/</code>. Follow the <code>hyperflow</code> doctrine.</p>
<h2>Steps</h2>
<ol>
<li><strong>Research</strong> the affected surface (files to read/modify/create, conventions, test patterns). If the request is actually a design question, redirect to <code>hyperflow-spec</code> and stop.</li>
<li><strong>Produce a batch graph.</strong> Order batches topologically; each sub-task = one coherent change nameable in a single conventional-commit subject. <strong>Split any sub-task</strong> that touches >5 files, >500 LOC, spans 2+ subsystems, or would take a reviewer >10 min to grasp.</li>
<li><strong>Write <code>.hyperflow/tasks/<slug>.md</code></strong> with: status table (progress, branch, commit cadence) → Goal → Why → Scope-at-a-glance table → Affected files (created/modified) → Execution plan (batch graph) → Batches (each sub-task with role, files, complexity, acceptance criteria, commit-message stub) → Verification plan.</li>
<li><strong>Print</strong> a one-line summary: <code>Plan ready — .hyperflow/tasks/<slug>.md (N batches, M sub-tasks)</code>.</li>
<li><strong>Hand off</strong>: invoke the <code>hyperflow-dispatch</code> skill with the task slug.</li>
</ol>
<h2>Rules</h2>
<ul>
<li>No implementation code; no source edits.</li>
<li>Single-batch plans for multi-file work are an anti-pattern — decompose.</li>
<li>Always include a concrete verification plan.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-spec" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-spec</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-spec/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow design phase.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-spec — design phase (Antigravity single-agent)</h1>
<p>This phase is <strong>thinking, not building</strong>. No code until the design is approved. Follow the <code>hyperflow</code> doctrine (autonomy, file-first, AskUserQuestion gates).</p>
<h2>Steps</h2>
<ol>
<li><strong>Research first.</strong> Read the relevant code, <code>AGENTS.md</code>, and <code>.hyperflow/memory/*</code> if present. Map the affected surface yourself. Do not ask what the code answers.</li>
<li><strong>Ask 2-5 clarifying questions</strong> (floor: 2) via AskUserQuestion — only the <em>what/which/where</em> the code can't resolve. Multi-option questions mark one <code>(Recommended)</code>; binary ones don't.</li>
<li><strong>Propose 2-3 approaches</strong> with one-line pros/cons/fit each. Recommend one; let the user pick.</li>
<li><strong>Design section-by-section.</strong> Write the design to <code>.hyperflow/specs/<slug>.md</code> 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 <code>Approve all / Revise <section></code>.</li>
<li><strong>On approval</strong>, hand off: invoke the <code>hyperflow-scope</code> skill with the spec path.</li>
</ol>
<h2>Rules</h2>
<ul>
<li>Never write implementation code here.</li>
<li>Never inflate a small task into a spec — economy matters. Trivial-clear requests skip straight to <code>hyperflow-scope</code>.</li>
<li>The spec file is the artefact; chat shows only a short pointer to it.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-status" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-status</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-status/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow project status.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-status — read-only state (Antigravity single-agent)</h1>
<p>One-screen view of hyperflow project state. <strong>Read-only</strong> — never edits files or runs work. Follow the <code>hyperflow</code> doctrine.</p>
<h2>Steps</h2>
<ol>
<li>Read <code>.hyperflow/tasks/*.md</code>; for each, report the status block (progress bar, sub-tasks done/total, branch).</li>
<li>Count <code>.hyperflow/specs/<em>.md</code> and <code>.hyperflow/audits/</em>.md</code>.</li>
<li>Count <code>.hyperflow/memory/*</code> entries.</li>
<li>Print a compact summary: active tasks + their progress, spec/audit counts, memory size. If <code>.hyperflow/</code> is absent, say so and suggest <code>hyperflow-scaffold</code>.</li>
</ol>
<h2>Rules</h2>
<ul>
<li>Never modify any file. Never dispatch work. Output is a single status block.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-sticky" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-sticky</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-sticky/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow auto-routing mode.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-sticky — auto-routing mode (Antigravity single-agent)</h1>
<p>Control hyperflow's auto-routing aggressiveness. Follow the <code>hyperflow</code> doctrine.</p>
<h2>Modes</h2>
<ul>
<li><strong>on</strong> — every task-shaped message routes through a hyperflow workflow.</li>
<li><strong>auto</strong> (default) — only messages whose first verb matches the routing table (build/fix/audit/scope/design/ship…) route.</li>
<li><strong>off</strong> — no auto-routing; hyperflow runs only when a <code>/hyperflow*</code> command is explicitly invoked.</li>
</ul>
<h2>Steps</h2>
<ol>
<li>Read the requested mode (on / auto / off).</li>
<li>Write it to <code>.hyperflow/.sticky-mode</code> (one word).</li>
<li>The core <code>hyperflow</code> skill reads this on each task to decide whether to auto-route.</li>
<li>Print the new mode.</li>
</ol>
<h2>Rules</h2>
<ul>
<li>This only changes routing behavior — it never runs work. Default is <code>auto</code> when the file is absent.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="hyperflow-trace" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>hyperflow-trace</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/hyperflow-trace/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Hyperflow debugging.</p>
                  
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>hyperflow-trace — root-cause phase (Antigravity single-agent)</h1>
<p>Find the root cause before changing anything. Follow the <code>hyperflow</code> doctrine.</p>
<h2>Steps</h2>
<ol>
<li><strong>Reproduce / locate.</strong> Read the error, stack trace, or failing test. Identify the exact failing line and the observed-vs-expected behavior.</li>
<li><strong>5 Whys.</strong> Trace the causal chain backward — keep asking "why" until you reach the true cause, not a symptom.</li>
<li><strong>Hypotheses.</strong> List the 2-4 most plausible causes. For each, state a cheap test (read a file, add a log, run one test) that confirms or rules it out. Test them — narrow to the real cause.</li>
<li><strong>Confirm</strong> the root cause with evidence (a failing assertion, a value print, a reproduced path). Do not patch on a guess.</li>
<li><strong>Fix</strong> the root cause minimally. Add or update a test that would have caught it (characterization test before behavior change).</li>
<li><strong>Verify</strong>: re-run the failing case + the surrounding suite. Self-review the diff (L1-L3). Commit as <code>fix(<scope>): <root cause></code> (conventional, lowercase).</li>
</ol>
<h2>Rules</h2>
<ul>
<li>Never blind-patch a symptom to make an error message disappear.</li>
<li>No behavior change beyond the fix unless asked.</li>
<li>If the root cause is unclear after hypothesis testing, surface what you found and what's still unknown — don't ship a speculative patch.</li>
</ul></div>
                </div>
              </div><div class="gist-card" data-skill-slug="scaffold" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>scaffold</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/scaffold/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when starting hyperflow in a new project, refreshing the .</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Write</span><span class="tool-pill" data-astro-cid-vaomz7ca>Edit</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(git:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Glob</span><span class="tool-pill" data-astro-cid-vaomz7ca>Grep</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Scaffold</h1>
<p>One-shot project setup. Analyzes the codebase, builds the <code>.hyperflow/</code> cache, seeds the memory skeleton, and optionally installs detection shims for other AI tools. Does not start the spec → scope → dispatch chain — invoke <code>/hyperflow:spec</code> (or <code>/hyperflow:scope</code>) when you're ready for that.</p>
<h2>Step 1 — Analysis Cache</h2>
<p>Check for <code>.hyperflow/</code> at project root.</p>
<p><strong>If absent — dispatch parallel searchers (single message, six Agent calls):</strong></p>
<table><thead><tr>
<th>Label</th>
<th>File generated</th>
<th>Discovers</th>
</tr></thead><tbody>
<tr>
<td><code>Searcher — analyzing tech stack</code></td>
<td><code>profile.md</code></td>
<td>Name, language, framework, build commands</td>
</tr>
<tr>
<td><code>Searcher — mapping folder structure</code></td>
<td><code>architecture.md</code></td>
<td>Dirs, patterns, routing, data flow</td>
</tr>
<tr>
<td><code>Searcher — extracting conventions</code></td>
<td><code>conventions.md</code></td>
<td>Naming, style, linting rules</td>
</tr>
<tr>
<td><code>Searcher — scanning dependencies</code></td>
<td><code>dependencies.md</code></td>
<td>UI lib, state, data fetching, DB, auth</td>
</tr>
<tr>
<td><code>Searcher — auditing test setup</code></td>
<td><code>testing.md</code></td>
<td>Runner, E2E, patterns, commands</td>
</tr>
<tr>
<td><code>Searcher — reading git workflow</code></td>
<td><code>git-workflow.md</code></td>
<td>Branches, commits, CI/CD, PR conventions</td>
</tr>
</tbody></table>
<p>See <a href="references/project-analysis.md">project-analysis.md</a> for what each file captures.</p>
<p><strong>If present — staleness check:</strong></p>
<p>Compute SHA256 of tracked config files, compare against <code>.hyperflow/.checksums</code>. Refresh only stale files. Print <code>Refreshing — <comma-separated list of stale files></code>.</p>
<p><strong>After analysis:</strong></p>
<ul>
<li>Write <code>.hyperflow/.checksums</code> (SHA256 of <code>package.json</code>, <code>tsconfig.json</code>, eslint/biome config, etc.)</li>
<li>Append to <code>.gitignore</code> if <code>.hyperflow/</code> is not already excluded</li>
</ul>
<h2>Step 2 — Memory Skeleton</h2>
<p>Create <code>.hyperflow/memory/</code> if absent:</p>
<pre><code>
.hyperflow/memory/
├── doctrine.md          ← copied from skills/hyperflow/DOCTRINE.md
├── index.md
├── learnings.md         ← empty stub (populated by /hyperflow:dispatch wrap-up)
├── decisions.md
├── pitfalls.md
├── patterns.md
├── conventions.md
├── session-context.md   ← [populated by session-start hook, NOT by scaffold]
└── archive/.gitkeep
</code></pre>
<p><strong>session-context.md — populated by the session-start hook, not scaffold:</strong></p>
<p>Scaffold creates the empty <code>.hyperflow/memory/</code> directory; it does NOT write <code>session-context.md</code>. That file is generated at the start of each Claude Code session by <code>hooks/session-start</code>, which concatenates <code>.h</div>
                </div>
              </div><div class="gist-card" data-skill-slug="scope" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>scope</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/scope/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when the user has a clear-enough task and wants it decomposed into batched worker sub-tasks before any code is written.</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Write</span><span class="tool-pill" data-astro-cid-vaomz7ca>Edit</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(git:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Glob</span><span class="tool-pill" data-astro-cid-vaomz7ca>Grep</span><span class="tool-pill" data-astro-cid-vaomz7ca>AskUserQuestion</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Scope</h1>
<p>Decompose, don't build. Read-only with respect to source code. The only writes are to <code>.hyperflow/tasks/</code>, <code>.hyperflow/memory/</code>, and <code>.hyperflow/specs/</code>. When the task file is ready, hand off to <code>dispatch</code> (auto or with a gate, depending on chain mode).</p>
<p>This skill exercises <strong>Layer 0 (Project Analysis)</strong> for context, <strong>Layer 6 (Project Memory)</strong> for past-learning surfacing, and <strong>Layer 7 (Task Templates)</strong> for decomposition patterns. It also inherits the triage classification from <code>/hyperflow:spec</code> to size each batch correctly.</p>
<h2>Iron Rules</h2>
<ul>
<li><strong>Failure recovery (rule 14).</strong> Worker errors, malformed output, NEEDS_REVISION, and Reviewer errors follow the canonical policy in <a href="../hyperflow/failure-recovery.md"><code>skills/hyperflow/failure-recovery.md</code></a>. Retry → escalate → abort. Chain budget: 3 cumulative aborts.</li>
</ul>
<h2>Per-Step Agent Map (DOCTRINE rule 12 + 12.2)</h2>
<p>Every substantive step dispatches at least one Agent per DOCTRINE rule 12. Trivial steps per §12.1 may be performed inline by the orchestrator. Non-trivial Steps decompose into ≥ 2 named sub-phases per DOCTRINE rule 12.2.</p>
<table><thead><tr>
<th>Step</th>
<th>Sub-phase</th>
<th>Worker tier</th>
<th>Thinking tier</th>
<th>Notes</th>
</tr></thead><tbody>
<tr>
<td>0 — Chain mode</td>
<td>— (atomic)</td>
<td>—</td>
<td>—</td>
<td><code>AskUserQuestion</code> only; 12.2.8-exempt</td>
</tr>
<tr>
<td>0.4 — Triage (Classifier + Reviewer)</td>
<td>— (atomic)</td>
<td>Classifier (Sonnet) [if not inherited]</td>
<td><strong>Triage Reviewer</strong> (Sonnet) [if not inherited + P4 conditions not met]</td>
<td>Skipped entirely when chained from spec (spec's validated triage is canonical); on direct invocation, dispatches its own Classifier then Triage Reviewer; skips Triage Reviewer on P4 conditions; 12.2.8-exempt</td>
</tr>
<tr>
<td>0.5 — Ops choices</td>
<td>— (atomic)</td>
<td>—</td>
<td>—</td>
<td>Single <code>AskUserQuestion</code> batch; 12.2.8-exempt</td>
</tr>
<tr>
<td>1 — Route</td>
<td>— (atomic)</td>
<td>—</td>
<td>—</td>
<td>Single mechanical routing decision; 12.2.8-exempt</td>
</tr>
<tr>
<td>2 — Research</td>
<td>2a + 2b + 2c (P1 parallel)</td>
<td></td>
<td></td>
<td>Sub-phase aggregate handed to Step 3</td>
</tr>
<tr>
<td></td>
<td>2a — Surface mapping</td>
<td>Searcher × 2 (glob discovery + import-graph traversal)</td>
<td><strong>Reviewer</strong> (Sonnet)</td>
<td>P1; no inter-dependency with 2b/2c</td>
</tr>
<tr>
<td></td>
<td>2b — Semantic indexing</td>
<td>Searcher × 2 (type-system probe + symbol-graph probe)</td>
<td><strong>Reviewer</strong> (Sonnet)</td>
<td>P1; no inter-dependency with 2a/2c</td>
</tr>
<tr>
<td></td>
<td>2c — Convention scan</td>
<td>Searcher × 1 (test patterns + lint config; single-angle justified: no independent probe angle for config)</td>
<td><strong>Reviewer</strong> (Son</div>
                </div>
              </div><div class="gist-card" data-skill-slug="spec" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>spec</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/spec/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when the user is exploring a design idea, weighing approaches, or has an ambiguous request.</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Write</span><span class="tool-pill" data-astro-cid-vaomz7ca>AskUserQuestion</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Spec</h1>
<p>This phase is <strong>thinking, not building</strong>. No code until the user approves the design. On approval, the chain advances to <code>scope</code> → <code>dispatch</code>. The user picks the advancement mode at Step 0.</p>
<p>This skill drives <strong>Layer 0.5 (Task Triage)</strong> and <strong>Layer 4 (Brainstorming/Spec)</strong> from the doctrine. Multi-level review (L1–L5) runs later during <code>/hyperflow:dispatch</code> per the triage's chosen flow profile.</p>
<h2>Iron Rules</h2>
<ul>
<li><strong>Failure recovery (rule 14).</strong> Worker errors, malformed output, NEEDS_REVISION verdicts, and Reviewer errors across every dispatched agent (Classifier, Triage Reviewer, Searchers, Writers, Analyst, batched Reviewer) follow the canonical policy in <a href="../hyperflow/failure-recovery.md"><code>skills/hyperflow/failure-recovery.md</code></a>. Retry → escalate → abort. Chain budget: 3 cumulative aborts.</li>
</ul>
<h2>Per-Step Agent Map (DOCTRINE rule 12)</h2>
<p>Every substantive step dispatches at least one Agent per DOCTRINE rule 12. Trivial steps per §12.1 may be performed inline by the orchestrator.</p>
<table><thead><tr>
<th>Step</th>
<th>Sub-phase</th>
<th>Worker tier</th>
<th>Thinking tier</th>
<th>Notes</th>
</tr></thead><tbody>
<tr>
<td>0 — Chain mode</td>
<td>— (atomic)</td>
<td>—</td>
<td>—</td>
<td><code>AskUserQuestion</code> only (exempt)</td>
</tr>
<tr>
<td>0.5 — Operational choices</td>
<td>— (atomic)</td>
<td>—</td>
<td>—</td>
<td><code>AskUserQuestion</code> only (exempt)</td>
</tr>
<tr>
<td>1 — Triage</td>
<td>— (atomic)</td>
<td>—</td>
<td><strong>Classifier</strong> (Opus) · <strong>Triage Reviewer</strong> (Sonnet)</td>
<td>Atomic per §12.2.8: single Worker → Reviewer pair, no independent angles. Reviewer verdicts: <code>PASS</code> / <code>RECLASSIFY</code> / <code>ESCALATE</code> (DOCTRINE rule 15). Skips on P4 conditions; see body</td>
</tr>
<tr>
<td>2 — Context Exploration</td>
<td>2a + 2b (P1 parallel)</td>
<td>Searcher ×2 per sub-phase [P3 concurrent with Step 1]</td>
<td><strong>Reviewer</strong> (Sonnet) per sub-phase</td>
<td>P3: Steps 1+2 dispatched in same message; no coverage Reviewer at Step level (D4)</td>
</tr>
<tr>
<td></td>
<td>2a — Codebase surface mapping</td>
<td>Searcher ×2 (glob discovery + dependency graph)</td>
<td><strong>Reviewer</strong> (Sonnet)</td>
<td>Parallel with 2b</td>
</tr>
<tr>
<td></td>
<td>2b — Convention and test pattern scan</td>
<td>Searcher ×2 (test pattern probe + lint/config scan)</td>
<td><strong>Reviewer</strong> (Sonnet)</td>
<td>Parallel with 2a</td>
</tr>
<tr>
<td>3 — Multi-dim analysis</td>
<td>3a + 3b + 3c (P1 parallel)</td>
<td>Writer ×1–2 per sub-phase</td>
<td><strong>Reviewer</strong> (Sonnet) per sub-phase + <strong>Analyst</strong> (Opus) final synthesis</td>
<td>P4-skippable; <code>--thorough</code> always runs</td>
</tr>
<tr>
<td></td>
<td>3a — Intent and technical-fit analysis</td>
<td>Writer ×2 (user-intent angle + technical-fit angle</div>
                </div>
              </div><div class="gist-card" data-skill-slug="status" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>status</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/status/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when the user wants a one-screen view of current hyperflow project state — version, profile freshness, memory count, and live progress on every in-flight task.</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(git:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(ls:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(stat:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(date:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Glob</span><span class="tool-pill" data-astro-cid-vaomz7ca>Grep</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Status</h1>
<p>Read-only snapshot of the current hyperflow project, with live progress on every active task file. Standalone — does not auto-chain and is never invoked by other skills. Invoked manually via <code>/hyperflow:status</code>.</p>
<p>The skill has two sections:</p>
<ol>
<li><strong>Static snapshot</strong> — version, profile freshness, memory count</li>
<li><strong>In-flight work</strong> — per-task live progress (sub-tasks done/total, tokens, wall-clock, ETA)</li>
</ol>
<h2>What to read</h2>
<h3>Static snapshot</h3>
<table><thead><tr>
<th>Field</th>
<th>Source</th>
<th>Fallback</th>
</tr></thead><tbody>
<tr>
<td>Version</td>
<td>Latest git tag matching <code>v*</code> + tag commit date</td>
<td><code>(missing)</code></td>
</tr>
<tr>
<td>Profile</td>
<td><code>.hyperflow/profile.md</code> file modification time</td>
<td><code>(missing)</code></td>
</tr>
<tr>
<td>Memory</td>
<td>Line count of <code>.hyperflow/memory/index.md</code> minus header rows</td>
<td><code>(none)</code></td>
</tr>
<tr>
<td>Active tasks</td>
<td>Files matching <code>.hyperflow/tasks/*.md</code></td>
<td><code>(none)</code></td>
</tr>
</tbody></table>
<h3>In-flight work (per task file)</h3>
<p>For every <code>.hyperflow/tasks/*.md</code>, parse its <code>## Status</code> block (written by <code>/hyperflow:scope</code> at creation and updated by <code>/hyperflow:dispatch</code> after each sub-task PASS — see scope/SKILL.md Step 4):</p>
<table><thead><tr>
<th>Field</th>
<th>Source</th>
<th>Behaviour</th>
</tr></thead><tbody>
<tr>
<td>Slug</td>
<td>basename of the task file minus <code>.md</code></td>
<td>always present</td>
</tr>
<tr>
<td>Done / total</td>
<td><code>Sub-tasks: <done> / <total></code> from Status block</td>
<td>falls back to counting <code>[x]</code> vs <code>[x]</code>+<code>[ ]</code> checkboxes if Status missing</td>
</tr>
<tr>
<td>Done sub-task names</td>
<td>lines with <code>[x]</code> from the <code>## Batches</code> section</td>
<td>listed under the bar</td>
</tr>
<tr>
<td>Running sub-task</td>
<td>the first <code>[~]</code> checkbox (dispatch marks <code>~</code> while a sub-task is mid-flight)</td>
<td><code>(idle)</code> if none</td>
</tr>
<tr>
<td>Pending sub-task count</td>
<td>count of <code>[ ]</code> checkboxes</td>
<td>shown as <code>N pending</code></td>
</tr>
<tr>
<td>Tokens used</td>
<td><code>Tokens used:</code> line from Status block</td>
<td><code>(not tracked yet)</code> if Status absent</td>
</tr>
<tr>
<td>Wall-clock</td>
<td><code>Wall-clock:</code> line from Status block</td>
<td><code>(not started)</code> if no <code>Started:</code></td>
</tr>
<tr>
<td>ETA</td>
<td><code>ETA:</code> line from Status block</td>
<td><code>(computing)</code> if <3 sub-tasks done</td>
</tr>
</tbody></table>
<h2>How to compute each field</h2>
<h3>Version</h3>
<pre data-lang="bash"><code>
tag=$(git tag --sort=-v:refname | grep -E '^v[0-9]' | head -1)
released=$(git log -1 --format=%ci "$tag" 2>/dev/null | cut -d' '</div>
                </div>
              </div><div class="gist-card" data-skill-slug="sticky" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>sticky</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/sticky/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when the user wants to set auto-routing mode: on (every task-shaped message routes), auto (intent-verb messages route — default), or off (no auto-routing).</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Write</span><span class="tool-pill" data-astro-cid-vaomz7ca>Edit</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(rm:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(ls:*)</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Sticky</h1>
<p>Set per-project auto-routing mode. Three states:</p>
<table><thead><tr>
<th>State</th>
<th>Default?</th>
<th>Behavior</th>
</tr></thead><tbody>
<tr>
<td><code>auto</code></td>
<td>yes (when <code>.sticky</code> absent)</td>
<td><strong>Intent-detection routing</strong> — messages containing chain-starter verbs (<code>audit</code>, <code>debug</code>, <code>fix</code>, <code>brainstorm</code>, <code>scope</code>, <code>deploy</code>, <code>review</code>, …) auto-route. Pure conversation passes through.</td>
</tr>
<tr>
<td><code>on</code></td>
<td>—</td>
<td><strong>Full sticky</strong> — every task-shaped message routes, even without explicit intent verbs</td>
</tr>
<tr>
<td><code>off</code></td>
<td>—</td>
<td><strong>All auto-routing disabled</strong> — only explicit <code>/hyperflow:*</code> slash commands trigger chains</td>
</tr>
</tbody></table>
<p>Intent-detection is the floor — the user gets it without any opt-in (the orchestrator scans every user message for chain-starter verbs and routes when matched). Sticky <code>on</code> raises the ceiling; sticky <code>off</code> lowers the floor.</p>
<p>Full doctrine: <a href="../hyperflow/DOCTRINE.md">DOCTRINE.md</a> Layer 1 auto-routing clause (intent verb taxonomy + routing contract + bypass patterns).</p>
<h2>Subcommands</h2>
<table><thead><tr>
<th>Subcommand</th>
<th>Description</th>
</tr></thead><tbody>
<tr>
<td><code>on</code></td>
<td>Set state: on — full sticky routing on every task-shaped message</td>
</tr>
<tr>
<td><code>auto</code></td>
<td>Set state: auto — intent-verb routing only (the default)</td>
</tr>
<tr>
<td><code>off</code></td>
<td>Set state: off — disable ALL auto-routing including intent detection</td>
</tr>
<tr>
<td><code>status</code></td>
<td>Show current state (on / auto / off / when toggled)</td>
</tr>
</tbody></table>
<p>Default subcommand when none provided: <code>status</code>.</p>
<h2>State persistence</h2>
<p>Sticky state is stored at <code>.hyperflow/.sticky</code> (project-scoped, gitignored). File format:</p>
<pre><code>
state: on
since: 2026-05-17T14:30:00Z
trigger: user-mention   # or: explicit-toggle | session-default
</code></pre>
<p>The session-start hook reads this file and prints a one-line advisory when sticky is on (<code>Sticky mode: ON since 2026-05-17 14:30 — task-shaped messages auto-route through hyperflow</code>). Sticky persists across sessions until explicitly toggled off.</p>
<h2>Subcommand Details</h2>
<h3><code>on</code></h3>
<p>Write <code>.hyperflow/.sticky</code> with <code>state: on</code> + ISO-8601 timestamp + <code>trigger: explicit-toggle</code>. Print:</p>
<pre><code>
Sticky mode: ON (full routing)
Every task-shaped message now routes through hyperflow, even without intent verbs.
Disable with /hyperflow:sticky off · or relax to verb-only routing with /hyperflow:sticky auto.
</code></pre>
<h3><code>auto</code></h3>
<p>Write <code>.hyperflow/.sticky</code> with <code>state: auto</code> + timestamp. This is the defaul</div>
                </div>
              </div><div class="gist-card" data-skill-slug="trace" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>trace</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/trace/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports.</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(git:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(npm:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Bash(pnpm:*)</span><span class="tool-pill" data-astro-cid-vaomz7ca>Glob</span><span class="tool-pill" data-astro-cid-vaomz7ca>Grep</span><span class="tool-pill" data-astro-cid-vaomz7ca>Agent</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Trace</h1>
<p>Root cause, not symptom. Never patch over a bug without understanding why it happened.</p>
<p>Dispatcher and reviewer — Opus 4.8 (thinking-tier). Implementer/Searcher/Writer — Sonnet 4.6.</p>
<h2>Per-Step Agent Map (DOCTRINE rule 12)</h2>
<p>Every substantive step dispatches at least one Agent. Atomic steps (per DOCTRINE 12.2.8) are a single Worker → Reviewer pair with no independent angles to fan out.</p>
<table><thead><tr>
<th>Step</th>
<th>Status</th>
<th>Worker tier</th>
<th>Thinking tier</th>
<th>Notes</th>
</tr></thead><tbody>
<tr>
<td>1 — Reproduce</td>
<td>Atomic (12.2.8)</td>
<td>Searcher (Sonnet)</td>
<td><strong>Reviewer</strong> (Opus)</td>
<td>Runs if repro missing; single Worker→Reviewer pair</td>
</tr>
<tr>
<td>2 — Gather evidence</td>
<td>Atomic (12.2.8)</td>
<td>Searcher × 3 (Sonnet)</td>
<td><strong>Reviewer</strong> (Opus)</td>
<td>3 parallel Searchers → single Reviewer; one Worker-group→Reviewer pair</td>
</tr>
<tr>
<td>3 — Hypothesize</td>
<td>Atomic (12.2.8)</td>
<td><strong>Debugger</strong> (Opus)</td>
<td><strong>Reviewer</strong> (Opus)</td>
<td>Single Debugger (5 Whys + ranked hypotheses in one pass) → Reviewer</td>
</tr>
<tr>
<td>4 — Verify</td>
<td>2 sub-phases</td>
<td>Implementer × N (Sonnet)</td>
<td><strong>Debugger</strong> (Opus) · <strong>Reviewer</strong> (Sonnet)</td>
<td>4a: parallel Implementers → Sonnet Reviewer; 4b: Debugger re-evaluation → Reviewer</td>
</tr>
<tr>
<td>5 — Fix at root</td>
<td>Atomic (12.2.8)</td>
<td>Implementer × N (Sonnet)</td>
<td><strong>Reviewer</strong> (Opus)</td>
<td>N Implementers (one per file) → Opus Reviewer; single Worker-group→Reviewer pair</td>
</tr>
<tr>
<td>6 — Regression test</td>
<td>Atomic (12.2.8)</td>
<td>Writer (Sonnet)</td>
<td><strong>Reviewer</strong> (Opus)</td>
<td>Single Writer → single Reviewer; no parallel angle</td>
</tr>
<tr>
<td>7 — Memory + final</td>
<td>Atomic (12.2.8)</td>
<td>Writer (Sonnet)</td>
<td><strong>Reviewer</strong> (Opus)</td>
<td>Single Writer → integration Reviewer; no parallel angle</td>
</tr>
</tbody></table>
<h2>Step 1 — Reproduce</h2>
<p>Atomic — single Searcher → Reviewer pair (DOCTRINE 12.2.8). No parallel angles: artifact retrieval is a single-scope search when the symptom is unknown.</p>
<p>If the user supplied a stack trace, test name, or log snippet — skip the Worker dispatch entirely (Step 1 is then trivially fulfilled by existing input; proceed to Step 2).</p>
<p>Otherwise dispatch <code>Searcher — locating bug reproduction in recent changes/tests</code> (Sonnet).</p>
<p>Collect: failing test name or command, error message, stack trace, log lines, recent commits touching the affected surface.</p>
<p>Then dispatch <code><strong>Reviewer</strong> — confirming reproduction is valid</code> (Opus) with the collected artifacts.</p>
<p>Reviewer confirms:</p>
<ul>
<li>The failure is consistent and deterministic (or flags intermittent).</li>
<li>The error matches the stated symptom.</li>
<li>The repro is not a test-</div>
                </div>
              </div><div class="gist-card" data-skill-slug="workflow" data-astro-cid-vaomz7ca>
                <div class="gist-header" data-astro-cid-vaomz7ca>
                  <button class="gist-toggle" aria-label="Toggle skill content" data-astro-cid-vaomz7ca>
                    <svg class="toggle-icon" width="12" height="12" viewBox="0 0 12 12" data-astro-cid-vaomz7ca>
                      <path d="M4 2 L10 6 L4 10 Z" fill="currentColor" data-astro-cid-vaomz7ca></path>
                    </svg>
                  </button>
                  <svg class="file-icon" width="16" height="16" viewBox="0 0 16 16" fill="currentColor" data-astro-cid-vaomz7ca>
                    <path d="M2 1.75C2 .784 2.784 0 3.75 0h6.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16h-9.5A1.75 1.75 0 0 1 2 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h9.5a.25.25 0 0 0 .25-.25V6h-2.75A1.75 1.75 0 0 1 9 4.25V1.5Zm6.75.062V4.25c0 .138.112.25.25.25h2.688l-.011-.013-2.914-2.914-.013-.011Z" data-astro-cid-vaomz7ca></path>
                  </svg>
                  <span class="gist-filename" data-astro-cid-vaomz7ca>workflow</span>
                  <span class="gist-filetype" data-astro-cid-vaomz7ca>SKILL.md</span>
                  <a href="/skills/workflow/" class="gist-view-link" data-astro-cid-vaomz7ca>View full skill →</a>
                </div>
                <div class="gist-body" data-astro-cid-vaomz7ca>
                  <p class="gist-description" data-astro-cid-vaomz7ca>Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow.</p>
                  <div class="gist-tools" data-astro-cid-vaomz7ca>
                      <span class="tool-pill" data-astro-cid-vaomz7ca>Read</span><span class="tool-pill" data-astro-cid-vaomz7ca>Glob</span><span class="tool-pill" data-astro-cid-vaomz7ca>Grep</span><span class="tool-pill" data-astro-cid-vaomz7ca>AskUserQuestion</span><span class="tool-pill" data-astro-cid-vaomz7ca>Skill</span>
                    </div>
                </div>
                <div class="gist-content" style="display: none;" data-astro-cid-vaomz7ca>
                  <div class="gist-content-inner" data-astro-cid-vaomz7ca><h1>Workflow</h1>
<p>Big-task path for work that is too large for normal turn-by-turn orchestration: system-wide changes, large migrations, repo-wide audits, high-confidence verification, and task prompts that explicitly ask for a workflow.</p>
<ul>
<li>In Claude Code, use the host dynamic workflow runtime.</li>
<li>In Codex, run the portable workflow adapter with Codex subagents when exposed; otherwise run the same phases inline in the current thread.</li>
<li>In OpenCode, run the portable workflow adapter with Task/subagent dispatch when exposed; otherwise run the same phases inline in the current session.</li>
<li>In Antigravity, Desktop/web bridge mode, or any host that cannot preserve the adapter phases, say so in one line and route to <code>/hyperflow:scope</code> with <code>chain-mode=auto</code>.</li>
</ul>
<p>Claude Code dynamic workflows require Claude Code v2.1.154 or later and can be disabled by <code>/config</code>, managed settings, <code>~/.claude/settings.json</code>, or <code>CLAUDE<em>CODE</em>DISABLE_WORKFLOWS=1</code>. When disabled, use the portable adapter if the host is Codex or OpenCode; otherwise route to <code>/hyperflow:scope</code> with <code>chain-mode=auto</code>.</p>
<h2>Routing Rules</h2>
<ul>
<li>Run this skill in Claude Code, Codex, and OpenCode.</li>
<li>Auto-route here when triage returns <code>flow=deep</code> or <code>flow=scientific</code>, <code>scope=system-wide</code>, or the user says <code>big task</code>, <code>large migration</code>, <code>repo-wide audit</code>, <code>run a workflow</code>, or <code>dynamic workflow</code>.</li>
<li>Do not route here for moderate multi-file work, routine bug fixes, or a task that needs user sign-off between implementation stages. Big-task workflow runs should not depend on arbitrary mid-run user input; split sign-off-heavy work into separate workflows or use <code>spec -> scope -> dispatch</code>.</li>
<li>Do not set <code>/effort ultracode</code> or <code>xhigh</code> automatically. The user can enable <code>/effort ultracode</code> manually for session-wide workflow selection.</li>
</ul>
<h2>Provider Contracts</h2>
<h3>Claude Code Native Workflow</h3>
<p>When this skill runs, ask the Claude Code workflow runtime to create a dynamic workflow for <code>$ARGUMENTS</code>. The generated workflow must preserve Hyperflow's doctrine inside the worker prompts and must include these phases:</p>
<ol>
<li>Research and planning</li>
</ol>
<ul>
<li>Map affected files, dependency edges, tests, docs, and risk boundaries.</li>
<li>Read <code>.hyperflow/profile.md</code>, <code>.hyperflow/architecture.md</code>, <code>.hyperflow/conventions.md</code>, <code>.hyperflow/testing.md</code>, and <code>.hyperflow/memory/index.md</code> when present.</li>
<li>Produce a concise execution graph with parallelizable units and dependencies.</li>
</ul>
<ol>
<li>Parallel implementation or investigation</li>
</ol>
<ul>
<li>Fan out independent agents by subsystem or file family.</li>
<li>Keep each</div>
                </div>
              </div>
          </div>
        </div>

      <!-- 9. Usage / How It Works (from README) -->
      <div class="section readme-section" data-astro-cid-vaomz7ca>
          <h2 data-astro-cid-vaomz7ca>How It Works</h2>
          <div class="readme-content" data-astro-cid-vaomz7ca><p>Invoke a skill. Chain-starters auto-advance through the rest — no always-on orchestrator, no background process, everything in your terminal.</p>
<h3>Thinking / worker split</h3>
<p>The split is structural, not a setting — each tier does only what it's best at.</p>
<table><thead><tr>
<th>Tier</th>
<th>Models</th>
<th>Role</th>
</tr></thead><tbody>
<tr>
<td><strong>Thinking</strong></td>
<td>GPT-5.5 · Opus 4.8 · Gemini 3 Pro</td>
<td>Orchestrate, triage, brainstorm, review every output, run the final integration pass</td>
</tr>
<tr>
<td><strong>Worker</strong></td>
<td>GPT-5.4 fast mode · Sonnet 4.6 · Gemini 3.5 Flash</td>
<td>Execute in parallel — implement, search, write</td>
</tr>
</tbody></table>
<h3>Review at every granularity</h3>
<p>Worker → Reviewer is an iron rule. Independent sub-tasks fan out in parallel; each worker feeds its own thinking-tier reviewer before the batch advances. Every non-trivial phase decomposes into named sub-phases (<code>2a</code>, <code>2b</code>, <code>2c</code>…), each with its own reviewer. Per-batch reviewers do L1–L2 spot-checks; a final integration reviewer runs once over the cumulative diff. Each reviewer returns a verdict — <code>APPROVE</code> or <code>NEEDS_REVISION</code> (retry once with findings injected).</p>
<h3>Triage picks the depth</h3>
<p>Every task is classified — complexity, scope, risk, ambiguity — and assigned a flow profile, so effort matches the work instead of always running deep:</p>
<table><thead><tr>
<th>Profile</th>
<th>Use when</th>
<th>Workers</th>
<th>Budget</th>
</tr></thead><tbody>
<tr>
<td><code>fast</code></td>
<td>trivial single-file, reversible</td>
<td>1</td>
<td>≤30k</td>
</tr>
<tr>
<td><code>standard</code></td>
<td>simple/moderate, 2–5 files</td>
<td>1–2</td>
<td>≤100k</td>
</tr>
<tr>
<td><code>deep</code></td>
<td>complex / cross-cutting / system-wide</td>
<td>3+</td>
<td>300k</td>
</tr>
<tr>
<td><code>research</code></td>
<td>unknown territory, evaluation</td>
<td>3+ searchers</td>
<td>≤80k</td>
</tr>
<tr>
<td><code>creative</code></td>
<td>UI/UX exploration</td>
<td>1–2</td>
<td>≤150k</td>
</tr>
<tr>
<td><code>scientific</code></td>
<td>correctness-critical, proof work</td>
<td>2–3 + TDD</td>
<td>300k</td>
</tr>
</tbody></table>
<h3>Persona stitching</h3>
<p>15 composable expert personas — architect, api, db, frontend, ui, security, performance, scientific, refactor, bugfix, test, research, creative, devops, docs. Each task is tagged and the matching personas are stitched into the worker prompt in priority order: <code>security</code> frames every decision first, <code>creative</code> adapts last.</p>
<h3>Workflows for big tasks</h3>
<p>Hyperflow routes very large tasks to <code>/hyperflow:workflow</code> instead of forcing everything through turn-by-turn dispatch. Use it for system-wide changes, large migrations, repo-wide audits, and verification-heavy work.</p>
<p>...</div>
        </div>

      <!-- 10. Use Cases (from README) -->
      

      <!-- 11. FAQ (from README troubleshooting) -->
      

      <!-- 12. Bottom CTA -->
      <section class="detail-cta" data-astro-cid-qcigfm7x>
  <h2 class="detail-cta__headline" data-astro-cid-qcigfm7x>Ready to use hyperflow?</h2>
  <div class="detail-cta__actions" data-astro-cid-qcigfm7x>
    <button class="detail-cta__primary" data-copy-install="/plugin install hyperflow@claude-code-plugins-plus" data-astro-cid-qcigfm7x>
      <svg width="16" height="16" viewBox="0 0 16 16" fill="none" aria-hidden="true" data-astro-cid-qcigfm7x>
        <rect x="5" y="5" width="9" height="9" rx="1.5" stroke="currentColor" stroke-width="1.5" data-astro-cid-qcigfm7x></rect>
        <path d="M3 11V3a1 1 0 011-1h8" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" data-astro-cid-qcigfm7x></path>
      </svg>
      <span class="detail-cta__btn-text" data-astro-cid-qcigfm7x>Copy Install Command</span>
    </button>
    <a href="https://github.com/Mohammed-Abdelhady/hyperflow" class="detail-cta__secondary" target="_blank" rel="noopener" data-astro-cid-qcigfm7x>
        <svg width="16" height="16" viewBox="0 0 16 16" fill="currentColor" aria-hidden="true" data-astro-cid-qcigfm7x>
          <path d="M8 0C3.58 0 0 3.58 0 8c0 3.54 2.29 6.53 5.47 7.59.4.07.55-.17.55-.38 0-.19-.01-.82-.01-1.49-2.01.37-2.53-.49-2.69-.94-.09-.23-.48-.94-.82-1.13-.28-.15-.68-.52-.01-.53.63-.01 1.08.58 1.23.82.72 1.21 1.87.87 2.33.66.07-.52.28-.87.51-1.07-1.78-.2-3.64-.89-3.64-3.95 0-.87.31-1.59.82-2.15-.08-.2-.36-1.02.08-2.12 0 0 .67-.21 2.2.82.64-.18 1.32-.27 2-.27.68 0 1.36.09 2 .27 1.53-1.04 2.2-.82 2.2-.82.44 1.1.16 1.92.08 2.12.51.56.82 1.27.82 2.15 0 3.07-1.87 3.75-3.65 3.95.29.25.54.73.54 1.48 0 1.07-.01 1.93-.01 2.2 0 .21.15.46.55.38A8.013 8.013 0 0016 8c0-4.42-3.58-8-8-8z" data-astro-cid-qcigfm7x></path>
        </svg>
        View on GitHub
      </a>
  </div>
</section>

<script type="module">document.querySelectorAll("[data-copy-install]").forEach(t=>{t.addEventListener("click",async()=>{const a=t.dataset.copyInstall||"";await navigator.clipboard.writeText(a);const e=t.querySelector(".detail-cta__btn-text");if(e){const o=e.textContent;e.textContent="Copied!",t.classList.add("copied"),window.trackEvent&&window.trackEvent("install_copied",{plugin_name:a.split(" ").pop()||"",source:"detail_cta"}),setTimeout(()=>{e.textContent=o,t.classList.remove("copied")},2e3)}})});</script>

      <!-- 13. Related Plugins -->
      <div class="section" data-astro-cid-vaomz7ca>
          <h2 data-astro-cid-vaomz7ca>Related Plugins</h2>
          <div class="related-plugins" data-astro-cid-vaomz7ca>
            <a class="pcard" href="/plugins/agency-os">
  <h3>agency-os</h3>
  <p>Run your work like an AI agency, from a single Notion board. Agents discuss, plan, and execute tasks in parallel with dependency ordering and model routing.</p>
  <code>/plugin install agency-os@claude-code-plugins-plus</code>
  
</a><a class="pcard" href="/plugins/discovery-questionnaire">
  <h3>discovery-questionnaire</h3>
  <p>Generate custom discovery questionnaires for AI agency prospects</p>
  <code>/plugin install discovery-questionnaire@claude-code-plugins-plus</code>
  
</a><a class="pcard" href="/plugins/make-scenario-builder">
  <h3>make-scenario-builder</h3>
  <p>Create Make.com (Integromat) scenarios with AI assistance</p>
  <code>/plugin install make-scenario-builder@claude-code-plugins-plus</code>
  
</a><a class="pcard" href="/plugins/n8n-workflow-designer">
  <h3>n8n-workflow-designer</h3>
  <p>Design complex n8n workflows with AI assistance - loops, branching, error handling</p>
  <code>/plugin install n8n-workflow-designer@claude-code-plugins-plus</code>
  
</a><a class="pcard" href="/plugins/roi-calculator">
  <h3>roi-calculator</h3>
  <p>Calculate and present ROI for AI automation projects</p>
  <code>/plugin install roi-calculator@claude-code-plugins-plus</code>
  
</a><a class="pcard" href="/plugins/sow-generator">
  <h3>sow-generator</h3>
  <p>Generate professional Statements of Work for AI projects</p>
  <code>/plugin install sow-generator@claude-code-plugins-plus</code>
  
</a>
          </div>
        </div>

      <!-- 14. Tags Footer -->
      <div class="tags-footer" data-astro-cid-vaomz7ca>
          <span class="tags-label" data-astro-cid-vaomz7ca>Tags</span>
          <div class="tags-list" data-astro-cid-vaomz7ca>
            <span class="tag" data-astro-cid-vaomz7ca>claude-code-plugin</span><span class="tag" data-astro-cid-vaomz7ca>multi-agent</span><span class="tag" data-astro-cid-vaomz7ca>dynamic-workflows</span><span class="tag" data-astro-cid-vaomz7ca>workflow-chain</span><span class="tag" data-astro-cid-vaomz7ca>triageflow</span><span class="tag" data-astro-cid-vaomz7ca>personas</span><span class="tag" data-astro-cid-vaomz7ca>flow-profiles</span><span class="tag" data-astro-cid-vaomz7ca>code-review</span><span class="tag" data-astro-cid-vaomz7ca>project-memory</span><span class="tag" data-astro-cid-vaomz7ca>multi-tool</span>
          </div>
        </div>
    </div>
  </div>

  <script type="module">const c=document.getElementById("copy-btn"),a=document.querySelector(".install-command");c&&a&&c.addEventListener("click",async()=>{const t=a.textContent||"";await navigator.clipboard.writeText(t),c.textContent="Copied!",c.classList.add("copied"),window.trackEvent&&window.trackEvent("install_copied",{plugin_name:t.split(" ").pop()||"",source:"plugin_detail"}),setTimeout(()=>{c.textContent="Copy",c.classList.remove("copied")},2e3)});document.querySelectorAll(".gist-toggle").forEach(t=>{t.addEventListener("click",()=>{const e=t.closest(".gist-card");if(!e)return;const n=e.querySelector(".gist-content"),o=t.querySelector(".toggle-icon");if(!n||!o)return;const l=n.style.display!=="none";n.style.display=l?"none":"block",o.style.transform=l?"":"rotate(90deg)",e.classList.toggle("expanded",!l)})});document.querySelectorAll(".gist-header").forEach(t=>{t.addEventListener("click",e=>{const n=e.target;if(n.closest("a")||n.closest(".gist-toggle"))return;const o=t.querySelector(".gist-toggle");o&&o.click()})});const s=document.getElementById("expand-all-btn");if(s){let t=!1;s.addEventListener("click",()=>{t=!t,s.textContent=t?"Collapse All":"Expand All",document.querySelectorAll(".gist-card").forEach(e=>{const n=e.querySelector(".gist-content"),o=e.querySelector(".toggle-icon");!n||!o||(n.style.display=t?"block":"none",o.style.transform=t?"rotate(90deg)":"",e.classList.toggle("expanded",t))})})}document.querySelectorAll("[data-expandable]").forEach(t=>{const e=t.querySelector(".readme-content");if(!e||e.scrollHeight<=400)return;e.classList.add("truncated");const n=document.createElement("button");n.className="show-more-btn",n.textContent="Show more",n.addEventListener("click",()=>{const o=e.classList.contains("truncated");e.classList.toggle("truncated",!o),n.textContent=o?"Show less":"Show more"}),e.insertAdjacentElement("afterend",n)});</script>

    </main>

    <!-- Footer -->
    <footer data-astro-cid-37fxchfa>
        <div class="footer-inner" data-astro-cid-37fxchfa>
            <div class="footer-signup-row" data-astro-cid-37fxchfa>
                <h4 data-astro-cid-37fxchfa>Stay in the Loop</h4>
                <form data-signup-form="footer" class="footer-signup-form" data-astro-cid-37fxchfa>
                    <input type="email" name="email" placeholder="you@example.com" required data-astro-cid-37fxchfa>
                    <input type="text" name="website" tabindex="-1" autocomplete="off" aria-hidden="true" style="position:absolute;left:-9999px;opacity:0;height:0;width:0;" data-astro-cid-37fxchfa>
                    <button type="submit" data-astro-cid-37fxchfa>Subscribe</button>
                </form>
                <p class="footer-form-note" data-astro-cid-37fxchfa>No spam. Unsubscribe anytime.</p>
            </div>

            <div class="footer-columns" data-astro-cid-37fxchfa>
                <div class="footer-col" data-astro-cid-37fxchfa>
                    <h5 data-astro-cid-37fxchfa>Product</h5>
                    <ul data-astro-cid-37fxchfa>
                        <li data-astro-cid-37fxchfa><a href="/explore" data-astro-cid-37fxchfa>Explore</a></li>
                        <li data-astro-cid-37fxchfa><a href="/skills" data-astro-cid-37fxchfa>Skills</a></li>
                        <li data-astro-cid-37fxchfa><a href="/cowork" data-astro-cid-37fxchfa>Cowork</a></li>
                        <li data-astro-cid-37fxchfa><a href="/compare-marketplaces" data-astro-cid-37fxchfa>Compare</a></li>
                        <li data-astro-cid-37fxchfa><a href="/tools" data-astro-cid-37fxchfa>Tools</a></li>
                    </ul>
                </div>
                <div class="footer-col" data-astro-cid-37fxchfa>
                    <h5 data-astro-cid-37fxchfa>Resources</h5>
                    <ul data-astro-cid-37fxchfa>
                        <li data-astro-cid-37fxchfa><a href="/docs" data-astro-cid-37fxchfa>Docs</a></li>
                        <li data-astro-cid-37fxchfa><a href="/changelog" data-astro-cid-37fxchfa>Changelog</a></li>
                        <li data-astro-cid-37fxchfa><a href="/collections" data-astro-cid-37fxchfa>Collections</a></li>
                        <li data-astro-cid-37fxchfa><a href="/playbooks" data-astro-cid-37fxchfa>Playbooks</a></li>
                        <li data-astro-cid-37fxchfa><a href="/research" data-astro-cid-37fxchfa>Research</a></li>
                        <li data-astro-cid-37fxchfa><a href="/learning" data-astro-cid-37fxchfa>Learning</a></li>
                    </ul>
                </div>
                <div class="footer-col" data-astro-cid-37fxchfa>
                    <h5 data-astro-cid-37fxchfa>Company</h5>
                    <ul data-astro-cid-37fxchfa>
                        <li data-astro-cid-37fxchfa><a href="/community" data-astro-cid-37fxchfa>Community</a></li>
                        <li data-astro-cid-37fxchfa><a href="/community#hall-of-fame" data-astro-cid-37fxchfa>Hall of Fame</a></li>
                        <li data-astro-cid-37fxchfa><a href="https://github.com/jeremylongshore/claude-code-plugins" target="_blank" data-astro-cid-37fxchfa>GitHub</a></li>
                    </ul>
                </div>
                <div class="footer-col" data-astro-cid-37fxchfa>
                    <h5 data-astro-cid-37fxchfa>Legal</h5>
                    <ul data-astro-cid-37fxchfa>
                        <li data-astro-cid-37fxchfa><a href="/privacy" data-astro-cid-37fxchfa>Privacy</a></li>
                        <li data-astro-cid-37fxchfa><a href="/terms" data-astro-cid-37fxchfa>Terms</a></li>
                        <li data-astro-cid-37fxchfa><a href="/acceptable-use" data-astro-cid-37fxchfa>Acceptable Use</a></li>
                    </ul>
                </div>
            </div>

            <div class="footer-bottom" data-astro-cid-37fxchfa>
                <p class="footer-blurb" data-astro-cid-37fxchfa>Tons of Skills by <a href="https://intentsolutions.io" target="_blank" data-astro-cid-37fxchfa>Intent Solutions</a>. Marine. Citadel Grad. 20 years ops → self-taught dev → AI architect.</p>
                <p class="footer-copyright" data-astro-cid-37fxchfa>© 2026 Tons of Skills | <a href="https://intentsolutions.io" target="_blank" data-astro-cid-37fxchfa>Intent Solutions</a></p>
            </div>
        </div>
    </footer>

    <!-- Light theme global overrides (must be unscoped to target body/nav/footer) -->
    

    <!-- Email signup + killer-skill nomination forms.
         Posts to /api/forms/{signup,nominate} on the same origin. The endpoint
         is a tiny Node service on the VPS (`forms-api.service`, 127.0.0.1:8090)
         that forwards to the Slack webhook in /etc/intentsolutions/notify.env.
         Anti-spam: honeypot field `website`, email/URL regex, 8 KiB body cap,
         per-IP rate limit on the server. See
         intentsolutions-vps-runbook/docs/tonsofskills-forms-api.md. -->
    <script type="module">
      (() => {
        const flash = (btn, msg, ok = true, restoreMs = 3000) => {
          const orig = btn.dataset.origText ?? btn.textContent;
          if (!btn.dataset.origText) btn.dataset.origText = orig;
          btn.textContent = msg;
          btn.style.opacity = ok ? '0.85' : '1';
          btn.disabled = ok;
          if (!ok) setTimeout(() => {
            btn.textContent = orig;
            btn.style.opacity = '';
            btn.disabled = false;
          }, restoreMs);
        };

        const wireSignup = (form) => form.addEventListener('submit', async (e) => {
          e.preventDefault();
          const btn = form.querySelector('button[type="submit"]');
          const emailInput = form.querySelector('input[type="email"]');
          const honey = form.querySelector('input[name="website"]');
          const email = (emailInput?.value || '').trim();
          if (!/^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(email)) {
            flash(btn, 'Invalid email', false);
            return;
          }
          flash(btn, 'Subscribing…', true, 0);
          try {
            const r = await fetch('/api/forms/signup', {
              method: 'POST',
              headers: { 'content-type': 'application/json' },
              body: JSON.stringify({
                email,
                source: form.dataset.signupForm || 'unknown',
                website: honey?.value || ''
              })
            });
            if (r.ok) {
              flash(btn, "You're in!", true, 0);
              if (emailInput) emailInput.value = '';
            } else if (r.status === 429) {
              flash(btn, 'Slow down', false);
            } else {
              const j = await r.json().catch(() => ({}));
              flash(btn, j.error || 'Something went wrong', false);
            }
          } catch {
            flash(btn, 'Network error', false);
          }
        });

        const wireNomination = (form) => form.addEventListener('submit', async (e) => {
          e.preventDefault();
          const btn = form.querySelector('button[type="submit"]');
          const repoInput = form.querySelector('input[name="repo"]');
          const honey = form.querySelector('input[name="website"]');
          const repoUrl = (repoInput?.value || '').trim();
          if (!/^https:\/\/github\.com\/[^/\s]+\/[^/\s]+/.test(repoUrl)) {
            flash(btn, 'GitHub URL only', false);
            return;
          }
          flash(btn, 'Submitting…', true, 0);
          try {
            const r = await fetch('/api/forms/nominate', {
              method: 'POST',
              headers: { 'content-type': 'application/json' },
              body: JSON.stringify({
                repoUrl,
                source: form.dataset.nominationForm || 'unknown',
                website: honey?.value || ''
              })
            });
            if (r.ok) {
              flash(btn, 'Submitted!', true, 0);
              if (repoInput) repoInput.value = '';
            } else if (r.status === 429) {
              flash(btn, 'Slow down', false);
            } else {
              const j = await r.json().catch(() => ({}));
              flash(btn, j.error || 'Something went wrong', false);
            }
          } catch {
            flash(btn, 'Network error', false);
          }
        });

        const wireContact = (form) => form.addEventListener('submit', async (e) => {
          e.preventDefault();
          const btn = form.querySelector('button[type="submit"]');
          const nameInput = form.querySelector('input[name="name"]');
          const emailInput = form.querySelector('input[type="email"]');
          const messageInput = form.querySelector('textarea[name="message"]');
          const honey = form.querySelector('input[name="website"]');
          const name = (nameInput?.value || '').trim();
          const email = (emailInput?.value || '').trim();
          const message = (messageInput?.value || '').trim();
          if (name.length < 2) { flash(btn, 'Name required', false); return; }
          if (!/^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(email)) { flash(btn, 'Invalid email', false); return; }
          if (message.length < 10) { flash(btn, 'Tell me more', false); return; }
          flash(btn, 'Sending…', true, 0);
          try {
            const r = await fetch('/api/forms/contact', {
              method: 'POST',
              headers: { 'content-type': 'application/json' },
              body: JSON.stringify({
                name,
                email,
                message,
                source: form.dataset.contactForm || 'unknown',
                website: honey?.value || ''
              })
            });
            if (r.ok) {
              flash(btn, "Got it — back within 24h!", true, 0);
              if (nameInput) nameInput.value = '';
              if (emailInput) emailInput.value = '';
              if (messageInput) messageInput.value = '';
            } else if (r.status === 429) {
              flash(btn, 'Slow down', false);
            } else {
              const j = await r.json().catch(() => ({}));
              flash(btn, j.error || 'Something went wrong', false);
            }
          } catch {
            flash(btn, 'Network error', false);
          }
        });

        const init = () => {
          document.querySelectorAll('[data-signup-form]').forEach(wireSignup);
          document.querySelectorAll('[data-nomination-form]').forEach(wireNomination);
          document.querySelectorAll('[data-contact-form]').forEach(wireContact);
        };
        if (document.readyState === 'loading') {
          document.addEventListener('DOMContentLoaded', init);
        } else { init(); }
      })();
    </script>

    <!-- Theme Toggle Script -->
    <script>
        document.addEventListener('DOMContentLoaded', function() {
            var themeToggle = document.querySelector('.theme-toggle');
            if (themeToggle) {
                themeToggle.addEventListener('click', function() {
                    var current = document.documentElement.getAttribute('data-theme') || 'dark';
                    var next = current === 'dark' ? 'light' : 'dark';
                    document.documentElement.setAttribute('data-theme', next);
                    localStorage.setItem('theme', next);
                    var meta = document.querySelector('meta[name="theme-color"]');
                    if (meta) meta.setAttribute('content', next === 'dark' ? '#0a0a0c' : '#fafaf9');
                });
            }
            window.matchMedia('(prefers-color-scheme: light)').addEventListener('change', function(e) {
                if (!localStorage.getItem('theme')) {
                    document.documentElement.setAttribute('data-theme', e.matches ? 'light' : 'dark');
                }
            });
        });
    </script>

    <!-- Nav Scroll State -->
    <script>
        (function() {
            var nav = document.querySelector('nav');
            if (!nav) return;
            function onScroll() {
                if (window.scrollY > 20) {
                    nav.classList.add('scrolled');
                } else {
                    nav.classList.remove('scrolled');
                }
            }
            window.addEventListener('scroll', onScroll, { passive: true });
            onScroll();
        })();
    </script>

    <!-- Mobile Menu Script -->
    <script>
        document.addEventListener('DOMContentLoaded', function() {
            var menuToggle = document.querySelector('.mobile-menu-toggle');
            var navLinks = document.querySelector('.nav-links');
            var menuIcon = document.querySelector('.menu-icon');
            var closeIcon = document.querySelector('.close-icon');

            if (menuToggle && navLinks) {
                menuToggle.addEventListener('click', function() {
                    navLinks.classList.toggle('active');
                    document.body.classList.toggle('menu-open');

                    if (navLinks.classList.contains('active')) {
                        menuIcon.style.display = 'none';
                        closeIcon.style.display = 'block';
                    } else {
                        menuIcon.style.display = 'block';
                        closeIcon.style.display = 'none';
                    }
                });

                navLinks.querySelectorAll('a').forEach(function(link) {
                    link.addEventListener('click', function() {
                        navLinks.classList.remove('active');
                        document.body.classList.remove('menu-open');
                        menuIcon.style.display = 'block';
                        closeIcon.style.display = 'none';
                    });
                });

                document.addEventListener('click', function(e) {
                    if (navLinks.classList.contains('active') &&
                        !navLinks.contains(e.target) &&
                        !menuToggle.contains(e.target)) {
                        navLinks.classList.remove('active');
                        document.body.classList.remove('menu-open');
                        menuIcon.style.display = 'block';
                        closeIcon.style.display = 'none';
                    }
                });
            }

            // Track outbound link clicks (nav + footer)
            document.querySelectorAll('nav a[target="_blank"], footer a[target="_blank"]').forEach(function(link) {
                link.addEventListener('click', function() {
                    if (window.trackEvent) {
                        window.trackEvent('outbound_click', {
                            url: link.href,
                            link_text: link.textContent.trim()
                        });
                    }
                });
            });
        });
    </script>
</body>
</html>
Subcommand	Description
`list`	Print the registry: in-flight · completed-uncollected · stalled · errored
`show`	Print one agent's output buffer (`.hyperflow/background/.md`)
`cancel`	Cancel one specific in-flight agent
`cancel --all`	Cancel every in-flight agent (use before closing a session)
`prune`	Delete completed `.hyperflow/background/.md` files older than 7 days
Subcommand	Description
`generate`	Write the doctrine block into the project's `CLAUDE.md` (create the file if absent, append the block if not present, refresh if already present)
`refresh`	Same as `generate` — alias for clarity when the block already exists
`remove`	Remove the doctrine block from `CLAUDE.md` (preserves your own content; if the file becomes empty after removal, leave it as an empty file rather than delete)
`status`	Show whether the doctrine block is present, its version, when it was generated
`mode	manual\	off>`	Set the auto-bridge mode for this project. Writes `.hyperflow/.bridge-mode`. The session-start hook reads this and decides what to do
Mode	Behavior
`auto` (default when `.bridge-mode` is absent)	If `./CLAUDE.md` is missing the doctrine block OR has an outdated version, silently writes/refreshes the block and prints a one-line notice in session-start output. Zero user friction.
`manual`	Never writes. Prints a one-line advisory when the block is missing or outdated: `./CLAUDE.md doctrine block would be refreshed (version 4.11.0) — run /hyperflow:bridge refresh to apply`.
`off`	Does nothing. No writes, no advisories.
hyperflow

Installation

What It Does

Hyperflow

Skills (27)

Amplify

Per-Step Agent Map (DOCTRINE rule 12)

Inputs

Flow

Step 1 — Read intent (atomic · 12.2.8)

Audit

Iron Rules

Per-Step Agent Map (DOCTRINE rule 12)

Background

Subcommands

Subcommand Details

`list`

`show`

Bridge

Subcommands

Auto-bridge (default ON)

Cache

Storage

Subcommands

Step	Sub-phase	Worker tier	Thinking tier	Notes
1 — Resolve scope	—	—	—	Mechanical decision (exempt)
2 — Gather context	2a — Surface mapping	Searcher × 2 (glob + import-graph)	Sonnet Reviewer	Parallel
2 — Gather context	2b — Semantic indexing	Searcher × 2 (type-system + symbol-graph)	Sonnet Reviewer	Parallel
2 — Gather context	2c — Convention scan	Searcher × 1 (test patterns + lint config)	Sonnet Reviewer	Justified single-angle
2 — Gather context	2d — Aggregate coverage gate	—	Reviewer (Opus) verifies aggregate coverage	Thinking-tier coverage gate
3 — Review	3a — L1+L2 (syntax/format/naming)	—	Reviewer (Opus) × 2 (different file groups) + Sonnet Reviewer aggregates verdicts	Parallel Opus pair; justified single-tier (Opus are the workers at L1-L2)
3 — Review	3b — L3 (integration/security)	—	Reviewer (Opus) × 2 (integration + security) + Sonnet Reviewer aggregates verdicts	Parallel Opus pair; justified single-tier (L3 requires thinking-tier)
3 — Review	3c — L4+L5 (perf/scale/a11y/UX)	—	Reviewer (Opus) × 2 (perf/scale + a11y/UX) + Sonnet Reviewer aggregates verdicts	Parallel Opus pair; justified single-tier (L4-L5 requires thinking-tier)
4 — Findings synthesis	4a — Critical findings	Writer × 2 (evidence probe + impact analysis)	Sonnet Reviewer	Parallel