Menü
Create a standalone ticket (bug, improvement, or request)
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | ticket |
| description | Create a standalone ticket (bug, improvement, or request) |
| argument-hint | <project> <ticket-title> |
| model | sonnet |
| allowed-tools | Read, Write, AskUserQuestion |
| disable-model-invocation | true |
Arguments: $ARGUMENTS
Expected format: <project> <ticket-title> (e.g., acme fix-login-redirect)
Parse $ARGUMENTS to extract project and ticket-title. Convert ticket-title to kebab-case if needed. If either is missing, stop and tell the user:
"Usage: /pm:ticket "
Read <project>/pm-config.md if it exists (for project context).
Check if <project>/tickets/<ticket-title>.md already exists. If it does, ask the PM if she wants to overwrite it.
Ask the PM the following. Adapt based on what the title already makes clear. Do not ask redundant questions.
Use AskUserQuestion to gather:
Type: Is this a bug, an improvement to something existing, or a new small request?
Description: What needs to be done? (If the title is already clear, ask for any additional context.)
If bug:
Acceptance criteria: What does "done" look like? Ask for at least 2 verifiable conditions.
Computed values: If the ticket involves any computed value (sum, average, count, subtraction, percentage, ratio, score, or similar), ask: "What is the exact formula? Include what is computed, the inputs, the denominator if any, and any scope or filters."
Charts: If the ticket involves a chart or visualisation, ask for the full visual spec: chart type, X-axis labels and format, Y-axis unit and starting point, any overlay or comparison behaviour, tooltip fields, and legend.
Definitions: If the ticket depends on a defined term (e.g., "active user", "completed session"), ask: what is included, what is excluded, are the categories mutually exclusive, and what are the edge cases?
Priority (optional): Does this have a priority?
Size: How big is this?
If the size answer is M or L, ask: "This seems larger than a standalone ticket. Would you like to create a spec instead with /pm:spec <project> <feature-name>?"
If the PM confirms M or L and wants to proceed, continue.
Create directory <project>/tickets/ if it does not exist.
For bugs: read .claude/overrides/templates/ticket-bug.md if it exists, otherwise read ~/.claude/pm/templates/ticket-bug.md. Use it as the output structure. Set type: bug.
For improvements: read .claude/overrides/templates/ticket.md if it exists, otherwise read ~/.claude/pm/templates/ticket.md. Use it as the output structure. Set type: improvement.
For requests: read .claude/overrides/templates/ticket.md if it exists, otherwise read ~/.claude/pm/templates/ticket.md. Use it as the output structure. Set type: request.
If .claude/overrides/rules/frontmatter.md exists, Read and follow it instead of ~/.claude/pm/rules/frontmatter.md. Otherwise Read ~/.claude/pm/rules/frontmatter.md.
Fill in all fields from the interview answers and today's date. Write the result to <project>/tickets/<ticket-title>.md.
Run /pm:validate on the ticket file. If it fails, fix the issues before saving.
If .claude/overrides/rules/task-quality.md exists, Read and follow it instead of ~/.claude/pm/rules/task-quality.md. Otherwise Read ~/.claude/pm/rules/task-quality.md.
After writing, tell the PM:
<project>/tickets/<ticket-title>.md/pm:sync <project> <ticket-title> to push to GitHub IssuesCo-create a customer interview guide using Mom Test principles
Transform a feature idea or stakeholder request into an outcome brief using a 4-stage framework: behavior hypothesis, risk identification, cheap experiment design, and metric definition. Use this skill when the user shares a feature idea, a stakeholder request, a PRD, a spec, or any document describing something to build and wants to pressure-test it before committing engineering capacity. Trigger on phrases like "outcome brief", "analyze this feature", "is this worth building", "test this idea", "brief this", "run the 4 questions", or when the user pastes a feature description and asks for critical analysis. Requires an input: a feature idea, document, or stakeholder request to analyze.
Convert a spec into a task breakdown (local, for review before syncing)
Produce a strategic intelligence report covering industry trends, competitive benchmarks, and opportunity mapping. Use when the PM wants market research, competitive analysis, or strategic landscape overview. Trigger on phrases like "research", "competitive analysis", "market landscape", "industry trends", or when the user wants to understand the competitive environment before building.
Conduct a structured PM interview to gather requirements, then write a complete spec document ready for development. Use this skill whenever a PM wants to spec out a feature, write up product requirements, plan what needs to be built, or turn a rough idea into a formal spec. Trigger on phrases like "spec out", "write a spec", "document requirements", "plan this feature", or when a PM describes something they want to build.
Push local tasks and tickets to GitHub Issues, Jira Cloud, or Asana