mpx-report-issue-or-bug

Parse bug descriptions and place Fix/Verify tasks into .mpx/ phase checklists.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you consistently track bugs and issues inside the .mpx/ phase system so fix work is organized, discoverable, and tied to the right phases.

Core Features & Use Cases

  • Parses issue inputs into structured bug fields: extracts summary, severity, affected area, and optional reproduction steps.
  • Finds the best placement in existing phases: matches the affected area against headings, task descriptions, and phase scope to decide where the bugfix should go.
  • Updates project tracking documents (only .mpx/): adds Fix/Verify tasks to the correct checklist, updates ROADMAP.md, and records critical/high issues in SPEC.md.

Quick Start

Use the skill to track a bug by providing a one-line description and let it update the appropriate .mpx/ files for later execution.

Frequently Asked Questions about mpx-report-issue-or-bug

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

FAQPage Schema
How do I track bugs and issues within my project phase checklists?

To track bugs within project phase checklists, the skill parses issue descriptions and inserts paired Fix/Verify tasks into the correct `.mpx/phases/*/CHECKLIST.md` files, ensuring work is mapped to the appropriate development phase.

What is the process for logging a critical bug into roadmap and spec documentation?

Logging a critical bug involves parsing the issue to extract severity, then updating `.mpx/ROADMAP.md` and recording critical or high severity issues directly in `.mpx/SPEC.md` to surface them in project tracking documents.

How do I add a bugfix task to an existing phase using a one-line issue description?

Adding a bugfix task from a one-line description requires the skill to parse the input, match the affected area against existing phase scopes, and place the task into the most relevant `.mpx/` checklist or create a new bugfix phase.

Does bug tracking in this workflow require a specific severity labeling format?

Yes, bug tracking in this workflow requires enforcing a Fix/Verify task pairing that includes a `[severity: level]` tag, ensuring all logged issues carry standardized severity labeling for prioritization.

What are the limitations of documentation-only bug tracking for phase checklists?

The limitation of documentation-only bug tracking is that the skill operates strictly over `.mpx/` files to update checklists and specs, meaning it cannot execute code fixes or interact with external issue tracking systems outside this directory structure.