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 epics4---56# Ticket Creation Wizard78Interactive Q&A flow for creating well-formed tickets. Guides users through gathering essential details before delegating to ticketing agent.910## When to Use1112Activate when user says:13- "Create a ticket" / "New ticket" / "File a ticket"14- "Help me create a bug report"15- "I want to request a feature"16- "Create an epic for..."17- "Ticket wizard" / "Help me create"1819## Quick Start Flow2021**Step 1: Determine Ticket Type**22```23What type of ticket are you creating?24251. Bug - Something is broken or not working as expected262. Feature - New functionality or enhancement request273. Task - Work item or to-do284. Epic - Large initiative containing multiple issues29```3031**Step 2: Gather Details** (varies by type - see templates in references)3233**Step 3: Confirm and Create** - Review summary, then delegate to ticketing agent3435## Minimum Required Fields by Type3637| Type | Required Fields |38|------|-----------------|39| Bug | Title, Expected, Actual, Repro Steps, Severity |40| Feature | Title, Problem, Solution, Acceptance Criteria |41| Task | Title, Success Criteria |42| Epic | Title, Vision, Scope, Success Metrics |4344## Q&A Flow Summary4546### Bug Reports471. Brief description (one sentence)482. Expected vs actual behavior493. Reproduction steps (numbered list)504. Environment details (browser, device, OS)515. Severity assessment (Critical/High/Medium/Low)5253### Feature Requests541. Feature summary (one sentence)552. Problem statement (why is it needed?)563. Proposed solution (how should it work?)574. Acceptance criteria (how will we know it's done?)585. Priority (Must-have/Should-have/Nice-to-have/Future)596. Dependencies (optional)6061### Tasks621. Task description (one sentence)632. Context (why is this needed?)643. Success criteria654. Parent issue (optional)665. Estimate (Small/Medium/Large/X-Large)6768### Epics691. Epic title702. Vision (high-level goal)713. Problem space (what problems does this address?)724. Success metrics735. Scope (included deliverables)746. Out of scope (exclusions)757. Target timeline (optional)7677## Priority Mapping7879| User Says | Maps To |80|-----------|---------|81| Urgent, ASAP, Critical | `priority:critical` |82| Important, High, Blocking | `priority:high` |83| Normal, Medium, Standard | `priority:medium` |84| Low, Minor, Eventually | `priority:low` |8586## Label Suggestions8788Based on ticket content, suggest labels:8990| Content Indicator | Suggested Labels |91|-------------------|------------------|92| Authentication, login | `auth`, `security` |93| UI, button, display | `frontend`, `ui` |94| API, endpoint | `backend`, `api` |95| Database, query | `backend`, `database` |96| Performance, slow | `performance` |97| Mobile, responsive | `mobile` |98| Documentation | `documentation` |99| Security, vulnerability | `security`, `priority:high` |100101## Delegation Pattern102103After gathering all information, delegate to ticketing agent:104105```106Task:107 agent: "ticketing"108 task: "Create [type] ticket with the following details"109 context: |110 Type: [bug/feature/task/epic]111 Title: [title]112 [Full formatted ticket content from template]113 Priority: [priority]114 Labels: [suggested labels]115 acceptance_criteria:116 - Ticket created successfully117 - Ticket ID returned118 - Confirm ticket details match provided content119```120121**IMPORTANT:** This wizard gathers information interactively but **ALWAYS** delegates actual ticket creation to ticketing-agent. PM never creates tickets directly.122123## Navigation124125For detailed templates and Q&A flows:126127- **[Bug Report Template](./references/bug-template.md)** - Complete bug report Q&A flow and output format128- **[Feature Request Template](./references/feature-template.md)** - Feature request Q&A flow and output format129- **[Task Template](./references/task-template.md)** - Task creation Q&A flow and output format130- **[Epic Template](./references/epic-template.md)** - Epic creation Q&A flow and output format131- **[Smart Prompts](./references/smart-prompts.md)** - Eliciting better information from users132133## Example Quick Flow134135```136User: "I need to create a bug report"137138PM: "I'll help you create a well-formed bug report.139140**What type of issue?**1411. Bug 2. Feature 3. Task 4. Epic"142143User: "1 - bug"144145PM: "**Describe the bug in one sentence:**"146147User: "Checkout button unclickable on Safari"148149[Continue Q&A per bug template...]150151PM: "Here's your bug report: [formatted summary]152**Ready to create this ticket?**"153154User: "yes"155156PM: [Delegates to ticketing-agent with full content]157```158159See [ticketing-delegation.md](../../../../docs/guides/ticketing-delegation.md) for delegation protocol.
bobmatnyc