Player profile
Ruflo
An MIT-licensed coding-agent meta-harness, formerly Claude Flow, for coordinated Claude Code and Codex swarms, with team topologies, per-agent Git worktrees, and swarm lifecycle tools.
Profile
Where it fits
Ruflo is the renamed Claude Flow project. Its README positions it as a meta-harness around existing coding agents rather than a replacement model or coding CLI.
It belongs in Coordination And Team Systems because coordinated swarms are the central workflow. The ruflo-swarm plugin README documents native TeamCreate, SendMessage, and Task integration, multiple swarm topologies, per-agent Git worktrees, and MCP tools for swarm and agent lifecycle management. Check the selected plugin and CLI path rather than assuming every installation provides the full feature set.
Builder web analytics
Measure projects built with Ruflo
After a Ruflo-coordinated team ships a reviewed product change, separately configured analytics can inform the next team task.
This is an optional workflow, not a native Ruflo integration. Configure tracking on the deployed product and authenticated analytics access separately; Ruflo's MCP tools and agent lifecycle do not install Agent Analytics or report product events.
First loop to measure
- a team implements and reviews a product change
- the operator deploys it to a separately instrumented surface
- an agent with separately configured analytics access reads observed outcomes
- the operator scopes the next swarm task from that evidence
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including deployed page, signup, activation event, or funnel step. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which deployed page, signup, activation event, or funnel step moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.