Use when the user wants hyperflow's behavioral rules to apply outside the terminal CLI — in Claude Code Desktop, claude.ai web, or IDE extensions that don't load CLI plugins. Writes a managed doctrine block into the project's CLAUDE.md so autonomy + intent-routing + commit cadence + role separation + file-first rules carry over. Lossy (no slash commands, no actual skill dispatch) but useful.
Trigger with /hyperflow:bridge, "make hyperflow work in desktop", "make hyperflow work in claude.ai", "embed hyperflow doctrine in CLAUDE.md", "portable hyperflow rules".
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Use when the user wants hyperflow's behavioral rules to apply outside the terminal CLI — in Claude Code Desktop, claude.ai web, or IDE extensions that don't load CLI plugins. Writes a managed doctrine block into the project's CLAUDE.md so autonomy + intent-routing + commit cadence + role separation + file-first rules carry over. Lossy (no slash commands, no actual skill dispatch) but useful.
Trigger with /hyperflow:bridge, "make hyperflow work in desktop", "make hyperflow work in claude.ai", "embed hyperflow doctrine in CLAUDE.md", "portable hyperflow rules".
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.
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 <auto|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: /hyperflow:bridge mode manual.
What gets written
A fenced block in the project's ./CLAUDE.md (at the repo root, where Claude Code Desktop / web / CLI all look for it):
The fenced markers (hyperflow:doctrine:start / hyperflow:doctrine:end) let refresh find and replace ONLY the doctrine block, leaving everything else in your CLAUDE.md untouched. Place the block anywhere in CLAUDE.md; the bridge respects its position.
When to use
Situation
Use bridge?
You work exclusively in Claude Code CLI (terminal)
No — the plugin loads doctrine directly; bridge would duplicate
yes (described in CLAUDE.md as rules for the orchestrator to follow)
Per-task commit cadence
yes
yes
Role separation (workers execute, reviewers review)
yes
yes
File-first artefacts under .hyperflow/
yes
yes
Binary-gate rule (no recommendation on yes/no)
yes
yes
No-AI-attribution rule
yes
yes
Security blocklists
yes
yes
/hyperflow:* slash commands
yes
no — surfaces without the plugin can't dispatch named skills
Chain-mode Step-0 auto/manual question
yes
no — defaults to auto-style chain in CLAUDE.md mode
Operational pre-elections (commit/branch/push at scope Step 2.6)
yes
no — defaults applied per CLAUDE.md guidance
Per-step Worker → Reviewer dispatch templates from worker-prompt.md / reviewer-prompt.md
yes
partial — the role-separation rule preserves the spirit; exact prompts not embedded (would bloat CLAUDE.md)
Background agents, sticky mode, status skill, cache skill
yes
no — these need their own slash command surfaces
Adaptive flow profiles (fast / standard / deep)
yes
no — orchestrator infers from message complexity
Net coverage: ~70% of hyperflow's behavioral value. Slash commands and the infrastructure that wraps them are the missing 30%.
Subcommand Details
generate / refresh
Read the template at ~/.claude/plugins/cache/hyperflow-marketplace/hyperflow/<version>/templates/claude-md-doctrine.md (resolve current version from the active plugin install).
Substitute placeholders: __HYPERFLOW_VERSION__ → current plugin version, __GENERATED_AT__ → current UTC timestamp (ISO-8601).
Read the project's ./CLAUDE.md. Three cases:
File absent — create ./CLAUDE.md with just the doctrine block.
File exists, no existing doctrine block — append the doctrine block at the end of the file (preceded by one blank line if the file doesn't already end with a blank line).
File exists, doctrine block present — find the <!-- hyperflow:doctrine:start … --> and <!-- hyperflow:doctrine:end --> markers, replace everything between them (inclusive of the markers) with the new block. All other content in CLAUDE.md is preserved exactly.
Write the updated CLAUDE.md.
Print:
Wrote hyperflow doctrine block to ./CLAUDE.md (version 4.10.1).
Surfaces that load CLAUDE.md (Desktop, claude.ai web, IDE extensions that talk to API) will now honor:
· Autonomy rules
· Intent-based routing (audit/debug/fix/brainstorm/scope/deploy verbs)
· Per-task commit cadence
· Role separation (workers execute, reviewers review)
· File-first artefacts under .hyperflow/
· No AI attribution
· Security blocklists
Re-run `/hyperflow:bridge refresh` after updating the plugin to pick up doctrine changes.
What's NOT in the bridge: /hyperflow:* slash commands, plugin-loaded skill files, operational pre-elections. Those need the terminal CLI.
remove
Read ./CLAUDE.md. If absent or doctrine markers not present, print Nothing to remove — no hyperflow doctrine block in ./CLAUDE.md. and stop.
Find the <!-- hyperflow:doctrine:start … --> and <!-- hyperflow:doctrine:end --> markers; remove everything between them (inclusive of markers). Collapse adjacent blank lines so the file doesn't end up with a triple newline.
If CLAUDE.md is now empty (or only whitespace), leave it as an empty file rather than delete — the user may have other tooling that expects the file to exist.
Print Removed hyperflow doctrine block from ./CLAUDE.md. Surfaces that loaded the doctrine block will revert to default behaviour.
mode <auto|manual|off>
Write the chosen mode to .hyperflow/.bridge-mode. The file holds one word: auto, manual, or off. The session-start hook reads it on every CLI session start. Print one of:
Auto-bridge: AUTO — ./CLAUDE.md doctrine block is silently maintained on every CLI session start.
Auto-bridge: MANUAL — session start prints an advisory when the block is stale; you run /hyperflow:bridge refresh.
Auto-bridge: OFF — no advisories, no writes. Use /hyperflow:bridge generate manually if you want the block.
Defaults to auto when .bridge-mode is absent (so first install of hyperflow auto-bridges with no user action). Setting auto explicitly is a no-op write that just records the intent.
status
Read ./CLAUDE.md. Find the doctrine markers. Print one of:
Hyperflow doctrine block: PRESENT in ./CLAUDE.md
Version generated: 4.10.1
Generated at: 2026-05-17T15:30:00Z
Plugin current: 4.10.1
Status: up to date · or · update available (re-run /hyperflow:bridge refresh)
Hyperflow doctrine block: NOT PRESENT in ./CLAUDE.md
Use /hyperflow:bridge generate to add it.
Hyperflow doctrine block: NOT PRESENT (no ./CLAUDE.md in project root)
Use /hyperflow:bridge generate to create ./CLAUDE.md with the doctrine block.
Flow
Parse subcommand (default status).
Locate the project's ./CLAUDE.md (repo root).
Execute subcommand per the details above.
Print one-block confirmation.
Overview
/hyperflow:bridge is the user-facing interface for the CLAUDE.md doctrine bridge. It does NOT itself enforce the doctrine — it writes the rules into a file that surfaces outside the terminal CLI will load. Enforcement happens in those surfaces when the host loads CLAUDE.md at session start.
Prerequisites
Project root contains a writable ./ directory (the bridge writes ./CLAUDE.md).
Hyperflow plugin installed (the bridge reads its template from the plugin cache). If running outside the plugin context, the bridge falls back to a vendored copy in the plugin source tree.
generate / refresh — multi-line confirmation listing what surfaces now honor; what's NOT in the bridge.
remove — one-line confirmation.
status — three-field block (present / version / freshness).
Error Handling
Failure
Behavior
./CLAUDE.md not writable
Print explicit error; suggest chmod +w ./CLAUDE.md if permissions-related. Do NOT silently fall back to a hidden location.
Plugin template not found (running outside cached plugin)
Look up the template at <plugin-root>/templates/claude-md-doctrine.md relative to this SKILL.md's directory. If still not found, refuse with a clear error.
Existing doctrine block has malformed markers (one without the other)
Refuse to refresh; print the malformed file's line range and ask the user to fix the markers manually. Do NOT auto-repair — the user's content might be at risk.
Multiple doctrine blocks in one CLAUDE.md (duplicate)
Refuse and surface the line ranges of both. User decides which to keep.
User runs generate repeatedly
Idempotent — every run replaces the block with the latest template + timestamp. No duplication.
Examples
First-time setup for a Desktop user
You: /hyperflow:bridge generate
Wrote hyperflow doctrine block to ./CLAUDE.md (version 4.10.1).
Surfaces that load CLAUDE.md (Desktop, claude.ai web, IDE extensions that talk to API) will now honor:
· Autonomy rules
· Intent-based routing (audit/debug/fix/brainstorm/scope/deploy verbs)
· Per-task commit cadence
· Role separation (workers execute, reviewers review)
· File-first artefacts under .hyperflow/
· No AI attribution
· Security blocklists
Re-run `/hyperflow:bridge refresh` after updating the plugin to pick up doctrine changes.
What's NOT in the bridge: /hyperflow:* slash commands, plugin-loaded skill files, operational pre-elections. Those need the terminal CLI.
Status check
You: /hyperflow:bridge status
Hyperflow doctrine block: PRESENT in ./CLAUDE.md
Version generated: 4.10.0
Generated at: 2026-05-15T09:12:00Z
Plugin current: 4.10.1
Status: update available (re-run /hyperflow:bridge refresh)
Refresh after plugin update
You: /hyperflow:bridge refresh
Wrote hyperflow doctrine block to ./CLAUDE.md (version 4.10.1).
...
Remove
You: /hyperflow:bridge remove
Removed hyperflow doctrine block from ./CLAUDE.md. Surfaces that loaded the doctrine block will revert to default behaviour.
