v3-integration-architect — Claude Code subagent: what it does, install
v3-integration-architect — a Claude subagent that carries out ADR-001: folding claude-flow into agentic-flow@alpha as an extension and cutting 10,000+ duplicated lines.
no license ★ 850 updated 2026-10-26
.claude/agents/v3-integration-architect.mdWhat v3-integration-architect does
This subagent exists for one refactor. claude-flow and agentic-flow@alpha grew two copies of the same machinery, and ADR-001 says to keep one of them. claude-flow becomes a thin layer on top of the library instead of a rival implementation.
The work is split into phases running from week 7 to week 10: an adapter layer first, the core move second, removal of the compatibility shim last. It builds on parts that already exist in agentic-flow@alpha — SONA learning modes, Flash Attention, shared AgentDB memory over HNSW, 213 MCP tools and 19 hook types. Each overlapping pair comes with a number: SwarmCoordinator against Swarm System at 80%, AgentManager against Agent Lifecycle at 70%.
Two shell hooks bracket a run. The first asks npx agentic-flow@alpha --version and prints the overlap table. The second files whatever pattern came out of the task into memory with npx agentic-flow@alpha memory store-pattern. No package installed, and the version check falls through to a warning. Paths like services/agentic-flow-hooks/ and src/core/SwarmCoordinator.ts belong to the agentic-flow repo, so on an unrelated codebase there is nothing to migrate.
What it helps with
- strip duplicated code shared by claude-flow and agentic-flow
- port SwarmCoordinator and AgentManager onto the shared classes
- wire SONA modes and Flash Attention into existing code
- move task and session handling onto the agentic-flow layer
- record integration patterns in agent memory after each task
Example prompts for the agent
- Map the overlap with
agentic-flow@alphaand lay out the ADR-001 steps. - Move
SwarmCoordinatoronto the Swarm System fromagentic-flow@alphaand mark the old file for deletion. - Plan the task and session migration phase by phase, then list what breaks once the compatibility layer goes.
How to install v3-integration-architect
Manually: put the files in place
.claude/agents/v3-integration-architect.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/v3-integration-architect.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/v3-integration-architect.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about v3-integration-architect
How do I install v3-integration-architect in Claude Code?
Put the subagent file at .claude/agents/v3-integration-architect.md inside your project.
What does v3-integration-architect do?
It runs the ADR-001 migration so claude-flow stops re-implementing agentic-flow and extends it instead, taking 10,000+ duplicated lines out along the way.
What does the subagent need to run?
agentic-flow@alpha reachable through npx. The first hook checks the version and only warns when the package is missing.