How do I install the Mpx Parse Spec skill?

Run npx skillmds@latest add martinopolo/mpx-parse-spec in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mpx Parse Spec safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mpx Parse Spec?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mpx Parse Spec free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mpx Parse Spec?

MartinoPolo (@martinopolo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mpx Parse Spec by martinopolo — Agent Skill

Name: Mpx Parse Spec
Rating: 4.2 (5 reviews)
Author: MartinoPolo

File contents

Parse Specification

Wrapper skill for specification parsing. It validates .mpx/SPEC.md, then delegates decomposition to mpx-spec-analyzer.

Iron Law

DOCUMENTATION ONLY. Creates/updates .mpx/ files only. Never modifies source code.

Prerequisites

.mpx/SPEC.md must exist

SPEC.md remains the project-level source of truth for requirements for the entire project lifecycle. ROADMAP.md and phase CHECKLIST.md files are execution tracking artifacts derived from SPEC.md.

Workflow

Step 1: Validate SPEC.md

Read .mpx/SPEC.md
Ensure it contains requirements as checkbox items (- [ ] / - [x])
If malformed or ambiguous, ask user what to fix before parsing

Step 2: Spawn Spec Analyzer

Always call the dedicated analyzer agent:

Use Task tool:
      subagent_type: "mpx-spec-analyzer"
      prompt: "Read .mpx/SPEC.md and regenerate .mpx/ROADMAP.md and .mpx/phases/*/CHECKLIST.md. Treat SPEC as source of truth. Skip [x] requirements as already implemented, but retain them as dependency/context when needed. If any requirement is ambiguous, ask clarifying questions before finalizing output. Preserve all requirement detail (constraints and edge cases) in phase specs/tasks without losing information."

Step 3: Report

Return concise status:

Specification Parsed via Agent!

Files Updated:
      - .mpx/ROADMAP.md
      - .mpx/phases/.../CHECKLIST.md

Skipped as Implemented:
      - [requirements marked [x]]

Next:
      - Review `.mpx/ROADMAP.md` and phase checklists
      - Run `/mp-execute mpx`

Error Handling

No SPEC.md: "No specification found. Run /mpx-add-requirements first."
Malformed SPEC.md: ask user to clarify/fix ambiguous lines
Analyzer failure: report error and keep SPEC.md untouched

Notes

This skill is intentionally thin; logic lives in mpx-spec-analyzer
Use /mpx-add-requirements for interactive requirement collection/updates
Use this skill when users edited SPEC.md manually and want a fresh parse

---name: mpx-parse-specdescription: Parse .mpx/SPEC.md by spawning mpx-spec-analyzer. Regenerates ROADMAP.md and phase CHECKLIST.md files.---# Parse SpecificationWrapper skill for specification parsing. It validates `.mpx/SPEC.md`, then delegates decomposition to `mpx-spec-analyzer`.## Iron Law**DOCUMENTATION ONLY.** Creates/updates `.mpx/` files only. Never modifies source code.## Prerequisites- `.mpx/SPEC.md` must exist`SPEC.md` remains the project-level source of truth for requirements for the entire project lifecycle. `ROADMAP.md` and phase `CHECKLIST.md` files are execution tracking artifacts derived from `SPEC.md`.## Workflow### Step 1: Validate SPEC.md- Read `.mpx/SPEC.md`- Ensure it contains requirements as checkbox items (`- [ ]` / `- [x]`)- If malformed or ambiguous, ask user what to fix before parsing### Step 2: Spawn Spec AnalyzerAlways call the dedicated analyzer agent:```Use Task tool: subagent_type: "mpx-spec-analyzer" prompt: "Read .mpx/SPEC.md and regenerate .mpx/ROADMAP.md and .mpx/phases/*/CHECKLIST.md. Treat SPEC as source of truth. Skip [x] requirements as already implemented, but retain them as dependency/context when needed. If any requirement is ambiguous, ask clarifying questions before finalizing output. Preserve all requirement detail (constraints and edge cases) in phase specs/tasks without losing information."```### Step 3: ReportReturn concise status:```Specification Parsed via Agent!Files Updated: - .mpx/ROADMAP.md - .mpx/phases/.../CHECKLIST.mdSkipped as Implemented: - [requirements marked [x]]Next: - Review `.mpx/ROADMAP.md` and phase checklists - Run `/mp-execute mpx````## Error Handling- **No SPEC.md:** "No specification found. Run `/mpx-add-requirements` first."- **Malformed SPEC.md:** ask user to clarify/fix ambiguous lines- **Analyzer failure:** report error and keep `SPEC.md` untouched## Notes- This skill is intentionally thin; logic lives in `mpx-spec-analyzer`- Use `/mpx-add-requirements` for interactive requirement collection/updates- Use this skill when users edited `SPEC.md` manually and want a fresh parse

Frequently asked questions

Mpx Parse Spec