📖About & Usage

About

Merlin Sequencer decides the order in which Merlin’s team members tackle a task. It exists so that every job flows through the right minds at the right time—analyst first, then designer, builder, tester, reviewer—turning a list of assigned helpers into a clear, step‑by‑step dependency chain. When Merlin wants a custom flow, he can supply a sequence hint and the droid swaps in that order instead.

Given a task and its assigned agents, the droid validates the input, discards duplicates or malformed entries, and outputs a linear work order where each role’s output feeds the next. It never decides who should work on a task, nor does it dispatch assignments—it only builds the execution backbone. The default role ranking progresses from Sage through Archon, Forge, Argus, Merlin, and finally Albus, but that sequence can be overridden.

This droid is a pure software process that runs on demand without calling Claude. It belongs to the planner droid family, which counts 14 members shared between Merlin and Elrond. Although several planner droids exist across these agents, Merlin Sequencer is a one‑of‑a‑kind named instance, used exclusively by Merlin to structure his own execution plans.

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.