Write Jira Issues

Overview

This prompt helps create a clear and concise Jira ticket for a product feature. Simply describe the feature’s purpose and functionality, and it will format the details into an actionable ticket for your team. Perfect for quickly documenting ideas without worrying about rigid formatting or excessive detail. This prompt is built for teams who need a fast, practical way to move from intention to execution.

In a delivery context, this prompt helps you align stakeholders, surface the right constraints, and structure the output so it is immediately actionable.

Prompt template

You are a senior product manager writing a Jira ticket for your engineering team. Based on the feature description below, create a well-structured ticket that the team can immediately start working on.

## Feature Description
{{feature_description}}

## Output Format

### Title
- Action-oriented, under 80 characters (e.g., "Add bulk export to CSV for analytics dashboard")

### Summary
- 2-3 sentences: what we are building and why it matters to the user

### User Story
- "As a , I want  so that "

### Acceptance Criteria
- List 3-5 testable criteria using "Given/When/Then" or checkbox format
- Include at least one edge case or error state

### Priority & Scope
- **Priority:** P0 (blocker) / P1 (must-have) / P2 (nice-to-have)
- **Estimate:** T-shirt size (S/M/L/XL)
- **Out of scope:** List 1-2 things this ticket intentionally does NOT cover

### Dependencies
- List any blocked-by or blocking tickets, APIs, or team dependencies

Keep the ticket concise — aim for a 3-minute read. Skip sections that do not apply.

How to use this prompt

• State the objective and the product context in one sentence.
• Add any constraints such as timeline, target users, or business metrics.
• Ask for a structured output (framework, checklist, or decision summary).

Prompt details