agent-v3-integration-architect

Migrates claude-flow onto agentic-flow@alpha adapters to eliminate duplicate orchestration code.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill agent-v3-integration-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-v3-integration-architect
Source: https://github.com/ruvnet/claude-flow/tree/main/.agents/skills/agent-v3-integration-architect
Command: npx skills add https://github.com/ruvnet/claude-flow --skill agent-v3-integration-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agentic-flow.

What problem does it solve?

claude-flow duplicates thousands of lines of orchestration logic (SwarmCoordinator, AgentManager, TaskScheduler, SessionManager) that already exist in agentic-flow@alpha, creating maintenance burden and inconsistent behavior. This Skill guides the ADR-001 migration that replaces those parallel implementations with adapter layers over agentic-flow.

Core Features & Use Cases

  • Duplication Analysis & Adapter Design: Maps overlapping components (80% swarm overlap, 70% agent lifecycle, 60% task execution) and defines TypeScript adapter classes extending agentic-flow primitives.
  • Phased Migration Plan: Provides a three-phase plan covering foundation adapters, core migration of task/session handling, and removal of deprecated code targeting under 5,000 orchestration lines.
  • Performance Feature Integration: Integrates agentic-flow capabilities including SONA learning modes, Flash Attention (2.49x-7.47x speedup), AgentDB HNSW search, 213 MCP tools, and RL algorithms.
  • Use Case: A maintainer modernizing claude-flow v3 uses this Skill to plan and execute the migration from legacy SwarmCoordinator and AgentManager classes to agentic-flow equivalents while preserving backward compatibility.

Quick Start

Invoke the v3-integration-architect agent to analyze current claude-flow duplication and produce a phased agentic-flow@alpha integration plan with adapter code.

Frequently Asked Questions about agent-v3-integration-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate claude-flow to agentic-flow@alpha?

Follow the three-phase plan: build an adapter layer extending agentic-flow Agent classes, migrate swarm, task, and session management to agentic-flow equivalents, then remove deprecated implementations. A compatibility layer maintains backward compatibility during transition.

What duplicate code does the v3 integration eliminate?

The migration targets SwarmCoordinator (800+ lines, 80% overlap with agentic-flow swarms), AgentManager (1,736 lines, 70% overlap), TaskScheduler (500+ lines), and SessionManager, reducing orchestration code from 15,000+ to under 5,000 lines.

Does the migration preserve backward compatibility with claude-flow v2?

Yes, the strategy uses dual operation where old and new systems run in parallel, followed by gradual per-feature migration with parity validation, and only then deprecation of the old system.

What performance improvements does agentic-flow integration provide?

Targets include 2.49x-7.47x speedup from Flash Attention with 50-75% memory reduction, 150x-12,500x faster search via AgentDB HNSW indexing, and under 0.05ms adaptation using SONA real-time learning mode.

What are the risks of the agentic-flow migration?

Key risks include breaking changes in agentic-flow@alpha (mitigated by version pinning and adapters), performance regression (mitigated by continuous benchmarking), and migration complexity (mitigated by the phased compatibility-layer approach).