Menu
Interactive ticket creation wizard with Q&A flow for bugs, features, tasks, and epics
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/bobmatnyc/claude-mpm --skill mpm-ticket-wizardThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
MCP (Model Context Protocol) - Build AI-native servers with tools, resources, and prompts. TypeScript/Python SDKs for Claude Desktop integration.
Model Context Protocol (MCP) server build and evaluation guide, including local conventions for tool surfaces, config, and testing
Control monitoring server and dashboard
Based on SOC occupation classification
Showing SKILL.md
| name | mpm-ticket-wizard |
| description | Interactive ticket creation wizard with Q&A flow for bugs, features, tasks, and epics |
| version | 1.0.0 |
| category | mpm |
| user-invocable | true |
| tags | ["mpm","tickets","wizard","creation","pm-recommended"] |
| triggers | ["create ticket","new ticket","ticket wizard","help me create","file a bug","request feature","create epic","create task"] |
Interactive Q&A flow for creating well-formed tickets. Guides users through gathering essential details before delegating to ticketing agent.
Activate when user says:
Step 1: Determine Ticket Type
What type of ticket are you creating?
1. Bug - Something is broken or not working as expected
2. Feature - New functionality or enhancement request
3. Task - Work item or to-do
4. Epic - Large initiative containing multiple issues
Step 2: Gather Details (varies by type - see templates in references)
Step 3: Confirm and Create - Review summary, then delegate to ticketing agent
| Type | Required Fields |
|---|---|
| Bug | Title, Expected, Actual, Repro Steps, Severity |
| Feature | Title, Problem, Solution, Acceptance Criteria |
| Task | Title, Success Criteria |
| Epic | Title, Vision, Scope, Success Metrics |
| User Says | Maps To |
|---|---|
| Urgent, ASAP, Critical | priority:critical |
| Important, High, Blocking | priority:high |
| Normal, Medium, Standard | priority:medium |
| Low, Minor, Eventually | priority:low |
Based on ticket content, suggest labels:
| Content Indicator | Suggested Labels |
|---|---|
| Authentication, login | auth, security |
| UI, button, display | frontend, ui |
| API, endpoint | backend, api |
| Database, query | backend, database |
| Performance, slow | performance |
| Mobile, responsive | mobile |
| Documentation | documentation |
| Security, vulnerability | security, priority:high |
After gathering all information, delegate to ticketing agent:
Task:
agent: "ticketing"
task: "Create [type] ticket with the following details"
context: |
Type: [bug/feature/task/epic]
Title: [title]
[Full formatted ticket content from template]
Priority: [priority]
Labels: [suggested labels]
acceptance_criteria:
- Ticket created successfully
- Ticket ID returned
- Confirm ticket details match provided content
IMPORTANT: This wizard gathers information interactively but ALWAYS delegates actual ticket creation to ticketing-agent. PM never creates tickets directly.
For detailed templates and Q&A flows:
User: "I need to create a bug report"
PM: "I'll help you create a well-formed bug report.
**What type of issue?**
1. Bug 2. Feature 3. Task 4. Epic"
User: "1 - bug"
PM: "**Describe the bug in one sentence:**"
User: "Checkout button unclickable on Safari"
[Continue Q&A per bug template...]
PM: "Here's your bug report: [formatted summary]
**Ready to create this ticket?**"
User: "yes"
PM: [Delegates to ticketing-agent with full content]
See ticketing-delegation.md for delegation protocol.