mpx-project-workflow

Define spec-driven project workflows with SPEC.md, ROADMAP.md, and phase artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the problem of unclear, disconnected project workflows by providing a structured spec-driven process to align teams and artifacts.

Core Features & Use Cases

  • Defines essential artifacts (SPEC.md, ROADMAP.md, phases/NN-name/ CHECKLIST.md) and where they live.
  • Describes how to use HANDOFF.md for session continuity and how to parse specs into roadmaps and phases.
  • Provides best practices for phase design, dependencies, and task decomposition.

Quick Start

Run the /mpx-setup command to begin a spec-driven project workflow.

Frequently Asked Questions about mpx-project-workflow

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

FAQPage Schema
What is spec-driven software engineering workflow and when do I need it?

Spec-driven software engineering workflow aligns teams and artifacts through structured phases. You need it when facing unclear, disconnected project processes, requiring consistent progress tracking via SPEC.md, ROADMAP.md, and CHECKLIST.md to maintain continuity.

How do I set up a spec-driven project workflow with SPEC.md and ROADMAP.md?

Run the /mpx-setup command to begin a spec-driven project workflow. This establishes essential artifacts like SPEC.md and ROADMAP.md, parses specifications into phases, and sets up HANDOFF.md for session continuity and consistent progress tracking.

How does HANDOFF.md work for session continuity in project phases?

HANDOFF.md enables session continuity by documenting project state during transitions between execution phases. It works alongside CHECKLIST.md within phase directories to ensure consistent progress tracking and seamless context transfer across development sessions.

Can I use a spec-driven workflow for task decomposition and dependency management?

Yes, spec-driven workflow provides best practices for phase design, dependencies, and task decomposition. It parses specifications into roadmaps and phases, enabling structured breakdown of tasks and managing inter-phase dependencies for consistent project execution.

What are the limitations of using spec.md for project workflow guidance?

Spec-driven workflow guidance requires maintaining multiple artifacts including SPEC.md, ROADMAP.md, and CHECKLIST.md. Limitations include overhead for small projects and reliance on disciplined HANDOFF.md practices to ensure accurate progress tracking across phase transitions.