mpx-execute

Automate task execution across project phases by auto-selecting next actionable tasks.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MartinoPolo/mxp-claude-code --skill mpx-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mpx-execute
Source: https://github.com/MartinoPolo/mxp-claude-code/tree/main/skills/mpx-execute
Command: npx skills add https://github.com/MartinoPolo/mxp-claude-code --skill mpx-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates task execution across project phases by auto-selecting the next actionable phase and tasks.

Core Features & Use Cases

  • Auto-selects the next eligible phase based on ROADMAP.md status and dependencies.
  • Decides task scope and batches small tasks when appropriate, or executes single tasks conservatively.
  • Executes tasks with built-in review steps (spec compliance and code quality) and automatic progression.

Quick Start

Invoke /mpx-execute to let the agent auto-select and run the next tasks in the current or all remaining phases.

Frequently Asked Questions about mpx-execute

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

FAQPage Schema
How do I automate task execution across project phases?

Automating phased project execution involves auto-selecting the next eligible phase and tasks based on a roadmap. It applies to phase-based workflows by handling dependencies, determining task scope, and running built-in spec compliance and code quality reviews.

What is phase-based project execution and how does dependency management work?

Phase-based project execution organizes work into sequential stages where dependency management ensures tasks auto-progress only when prior phases are complete. It uses a roadmap file to track status and automatically selects the next eligible phase for execution.

How do I auto-select the next actionable tasks in a spec-driven workflow?

Auto-selecting the next actionable tasks in a spec-driven workflow requires evaluating a roadmap to determine phase status and dependencies. The execution process then batches or individually runs tasks while applying built-in spec compliance and code quality review steps.

Can I use automated task batching for phased project roadmaps?

Automated task batching for phased project roadmaps is supported by dynamically deciding task scope. It batches small tasks when appropriate for efficiency, or conservatively executes single tasks to maintain control over complex project phases.

Do I need a ROADMAP.md file to run automated phase execution?

A ROADMAP.md file is required for automated phase execution because the system auto-selects the next eligible phase based on its tracked status and dependencies. This structured task data is essential for orchestration and scope determination.

What are the limitations of automating phased project execution?

Limitations of automating phased project execution include reliance on phase-based roadmaps and spec-driven workflows. Without a defined roadmap file for status tracking and dependency resolution, the automated orchestration cannot determine the next actionable phase or task scope.