📖About & Usage

Owner agent — accountability this droid serves

Merlin must take each strategic step and turn it into a detailed work plan, then dispatch the right team members in the right sequence. MS-01 solves the sequencing: given a list of team members assigned to a task, it orders them properly.

Droid responsibility

MS-01 determines the order in which Merlin will involve each team member. It uses a standard workflow order by default (analyst, designer, builder, tester, reviewer), but Merlin can override it if the task calls for a different flow. This sequence forms the backbone of Merlin's execution plan.

What the droid actually does

• Takes a task and a list of team members assigned to it
• Orders them using the standard role sequence (analyst → designer → builder → tester → reviewer), or a custom sequence if Merlin provides one
• Validates the input for correct format and rejects duplicates or malformed data
• Outputs an ordered list where each team member's work depends on the previous one

Boundaries

• Only sequences linear workflows — team members execute one after another, never in parallel
• Does not decide which team members should work on a task (that's determined elsewhere)
• Does not create actual task assignments or dispatch anyone; only provides the execution sequence
• Does not modify the execution details for each team member

👤Owner

📚Recent initiatives

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