mp-to-prd

Create a PRD as a GitHub issue from project requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts passed requirements into a structured Product Requirements Document (PRD) that’s ready to be reviewed and tracked as a GitHub issue, reducing ambiguity and rework.

Core Features & Use Cases

  • Requirement-to-PRD drafting: Translates project requirements into user stories, scope, acceptance criteria, and technical/testing decisions tied to project context.
  • Codebase-aware module design: Reads existing project context from .mpx/CONTEXT.md and inspects package.json plus relevant structure to propose modules and what needs tests.
  • Approval-first issue creation: Shows the PRD draft to the user for approval before creating the labeled GitHub issue (optionally assigning a milestone).

Quick Start

Ask the AI to run mp-to-prd with your milestone name to generate a PRD as a GitHub issue.

Frequently Asked Questions about mp-to-prd

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

FAQPage Schema
How do I convert project requirements into a structured PRD as a GitHub issue?

Converting requirements into a PRD GitHub issue involves translating project needs into user stories, scope, and acceptance criteria, then creating a labeled issue via the gh CLI after draft approval.

What is the best way to generate acceptance criteria and module design from software requirements?

Generating acceptance criteria and module design from requirements involves reading project context files and inspecting repository structure to propose testable modules tied to your codebase.

Does this PRD generation approach require existing context files in the repository?

Yes, this PRD generation approach requires reading the .mpx/CONTEXT.md file for project context, while optionally using .mpx/DECISIONS.md to inform technical and testing decisions.

How do I add a milestone to a PRD issue created from project requirements?

Adding a milestone to a PRD issue occurs during creation, where the Skill optionally assigns milestones through the gh CLI after you review and approve the generated draft.

Can I review the PRD draft before it becomes a GitHub issue?

Yes, you can review the PRD draft before issue creation because the Skill uses an approval-first workflow, presenting the structured document for user validation before publishing via gh CLI.