mma-execute-plan

Dispatch Markdown plan tasks sequentially to a single worker session.

5|4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/zhixuan312/multi-model-agent --skill mma-execute-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mma-execute-plan
Source: https://github.com/zhixuan312/multi-model-agent/tree/main/packages/server/src/skills/mma-execute-plan
Command: npx skills add https://github.com/zhixuan312/multi-model-agent --skill mma-execute-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch plan-driven work from a Markdown plan file to a single worker session, enabling tasks to be executed in a controlled, sequential flow.

Core Features & Use Cases

  • Dispatches tasks from a plan file to a single worker session.
  • Executes selected tasks sequentially within one worktree, preserving plan order.
  • Supports choosing tasks via a tasks array and restricting execution to a specific plan file path.
  • Works with plan headings that exactly match task descriptors to ensure accurate execution.

Quick Start

Create or identify a plan file with numbered headings and invoke mma-execute-plan to run the desired tasks in order.

Frequently Asked Questions about mma-execute-plan

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

FAQPage Schema
How do I execute tasks from a Markdown plan file sequentially?▼

Executing tasks sequentially from a Markdown plan file requires numbered headings that match task descriptors, allowing a dispatcher to send selected tasks to a single worker session in order.

What is a plan dispatch worker session used for?▼

A plan dispatch worker session executes selected tasks from a plan file sequentially within a dedicated worktree, preserving the original plan order and ensuring accurate task-name matching.

How do I run specific tasks from a plan file in order?▼

Running specific tasks in order involves providing a tasks array and a single plan file path, which restricts execution to matching numbered headings and runs them sequentially in one worktree session.

Does plan task execution require exact heading name matching?▼

Plan task execution requires exact matching between task descriptors and plan headings to ensure accurate task identification and sequential execution within the dedicated worktree session.

Can I dispatch tasks from multiple plan files into one worker session?▼

This plan dispatch process uses a single plan file path for target paths, meaning it cannot combine tasks from multiple plan files into the same sequential worker session.