Ticket Creation Wizard
Interactive Q&A flow for creating well-formed tickets. Guides users through gathering essential details before delegating to ticketing agent.
When to Use
Activate when user says:
- "Create a ticket" / "New ticket" / "File a ticket"
- "Help me create a bug report"
- "I want to request a feature"
- "Create an epic for..."
- "Ticket wizard" / "Help me create"
Quick Start Flow
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
Minimum Required Fields by Type
| 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 |
Q&A Flow Summary
Bug Reports
- Brief description (one sentence)
- Expected vs actual behavior
- Reproduction steps (numbered list)
- Environment details (browser, device, OS)
- Severity assessment (Critical/High/Medium/Low)
Feature Requests
- Feature summary (one sentence)
- Problem statement (why is it needed?)
- Proposed solution (how should it work?)
- Acceptance criteria (how will we know it's done?)
- Priority (Must-have/Should-have/Nice-to-have/Future)
- Dependencies (optional)
Tasks
- Task description (one sentence)
- Context (why is this needed?)
- Success criteria
- Parent issue (optional)
- Estimate (Small/Medium/Large/X-Large)
Epics
- Epic title
- Vision (high-level goal)
- Problem space (what problems does this address?)
- Success metrics
- Scope (included deliverables)
- Out of scope (exclusions)
- Target timeline (optional)
Priority Mapping
| User Says |
Maps To |
| Urgent, ASAP, Critical |
priority:critical |
| Important, High, Blocking |
priority:high |
| Normal, Medium, Standard |
priority:medium |
| Low, Minor, Eventually |
priority:low |
Label Suggestions
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 |
Delegation Pattern
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.
Navigation
For detailed templates and Q&A flows:
Example Quick Flow
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.
1---2name: mpm-ticket-wizard3description: "Interactive ticket creation wizard with Q&A flow for bugs, features, tasks, and epics"4version: 1.0.05category: mpm6user-invocable: true7tags: [mpm, tickets, wizard, creation, pm-recommended]8triggers:9 - "create ticket"10 - "new ticket"11 - "ticket wizard"12 - "help me create"13 - "file a bug"14 - "request feature"15 - "create epic"16 - "create task"17---1819# Ticket Creation Wizard2021Interactive Q&A flow for creating well-formed tickets. Guides users through gathering essential details before delegating to ticketing agent.2223## When to Use2425Activate when user says:26- "Create a ticket" / "New ticket" / "File a ticket"27- "Help me create a bug report"28- "I want to request a feature"29- "Create an epic for..."30- "Ticket wizard" / "Help me create"3132## Quick Start Flow3334**Step 1: Determine Ticket Type**35```36What type of ticket are you creating?37381. Bug - Something is broken or not working as expected392. Feature - New functionality or enhancement request403. Task - Work item or to-do414. Epic - Large initiative containing multiple issues42```4344**Step 2: Gather Details** (varies by type - see templates in references)4546**Step 3: Confirm and Create** - Review summary, then delegate to ticketing agent4748## Minimum Required Fields by Type4950| Type | Required Fields |51|------|-----------------|52| Bug | Title, Expected, Actual, Repro Steps, Severity |53| Feature | Title, Problem, Solution, Acceptance Criteria |54| Task | Title, Success Criteria |55| Epic | Title, Vision, Scope, Success Metrics |5657## Q&A Flow Summary5859### Bug Reports601. Brief description (one sentence)612. Expected vs actual behavior623. Reproduction steps (numbered list)634. Environment details (browser, device, OS)645. Severity assessment (Critical/High/Medium/Low)6566### Feature Requests671. Feature summary (one sentence)682. Problem statement (why is it needed?)693. Proposed solution (how should it work?)704. Acceptance criteria (how will we know it's done?)715. Priority (Must-have/Should-have/Nice-to-have/Future)726. Dependencies (optional)7374### Tasks751. Task description (one sentence)762. Context (why is this needed?)773. Success criteria784. Parent issue (optional)795. Estimate (Small/Medium/Large/X-Large)8081### Epics821. Epic title832. Vision (high-level goal)843. Problem space (what problems does this address?)854. Success metrics865. Scope (included deliverables)876. Out of scope (exclusions)887. Target timeline (optional)8990## Priority Mapping9192| User Says | Maps To |93|-----------|---------|94| Urgent, ASAP, Critical | `priority:critical` |95| Important, High, Blocking | `priority:high` |96| Normal, Medium, Standard | `priority:medium` |97| Low, Minor, Eventually | `priority:low` |9899## Label Suggestions100101Based on ticket content, suggest labels:102103| Content Indicator | Suggested Labels |104|-------------------|------------------|105| Authentication, login | `auth`, `security` |106| UI, button, display | `frontend`, `ui` |107| API, endpoint | `backend`, `api` |108| Database, query | `backend`, `database` |109| Performance, slow | `performance` |110| Mobile, responsive | `mobile` |111| Documentation | `documentation` |112| Security, vulnerability | `security`, `priority:high` |113114## Delegation Pattern115116After gathering all information, delegate to ticketing agent:117118```119Task:120 agent: "ticketing"121 task: "Create [type] ticket with the following details"122 context: |123 Type: [bug/feature/task/epic]124 Title: [title]125 [Full formatted ticket content from template]126 Priority: [priority]127 Labels: [suggested labels]128 acceptance_criteria:129 - Ticket created successfully130 - Ticket ID returned131 - Confirm ticket details match provided content132```133134**IMPORTANT:** This wizard gathers information interactively but **ALWAYS** delegates actual ticket creation to ticketing-agent. PM never creates tickets directly.135136## Navigation137138For detailed templates and Q&A flows:139140- **[Bug Report Template](./references/bug-template.md)** - Complete bug report Q&A flow and output format141- **[Feature Request Template](./references/feature-template.md)** - Feature request Q&A flow and output format142- **[Task Template](./references/task-template.md)** - Task creation Q&A flow and output format143- **[Epic Template](./references/epic-template.md)** - Epic creation Q&A flow and output format144- **[Smart Prompts](./references/smart-prompts.md)** - Eliciting better information from users145146## Example Quick Flow147148```149User: "I need to create a bug report"150151PM: "I'll help you create a well-formed bug report.152153**What type of issue?**1541. Bug 2. Feature 3. Task 4. Epic"155156User: "1 - bug"157158PM: "**Describe the bug in one sentence:**"159160User: "Checkout button unclickable on Safari"161162[Continue Q&A per bug template...]163164PM: "Here's your bug report: [formatted summary]165**Ready to create this ticket?**"166167User: "yes"168169PM: [Delegates to ticketing-agent with full content]170```171172See [ticketing-delegation.md](../../../../docs/guides/ticketing-delegation.md) for delegation protocol.
bobmatnyc