---
name: briefing-to-ticket
description: >
  Converts messy, unstructured client briefings — such as voice-to-text transcripts, 
  WhatsApp/Slack messages, emails, or informal notes — into polished, structured 
  engineering tickets for Linear or Jira. Use this skill whenever a user shares a 
  raw client message, audio transcript, chaotic email, or informal description of a 
  problem and wants it turned into a ticket, issue, bug report, or task. Trigger even 
  if the user just says "make a ticket from this" or "turn this into a Jira issue" or 
  pastes a messy message and asks for a clean version. Also trigger when the user 
  mentions Linear, Jira, GitHub Issues, or any issue tracker alongside a raw briefing.
---

# Briefing → Engineering Ticket Converter

Turn any messy client communication into a clean, structured engineering ticket ready to drop into Linear, Jira, or any issue tracker.

## Core Behavior

1. **Read and understand** the full briefing, no matter how informal or chaotic.
2. **Identify the primary problem** — the most critical or urgent issue the client is actually describing. This becomes the main ticket.
3. **Separate secondary concerns** — unrelated requests, nice-to-haves, or scope creep go in the Notes section, not the main ticket body.
4. **Infer what's missing** — fill in reasonable defaults (e.g., infer Priority from urgency language, infer Type from whether it's a malfunction vs. a request).
5. **Output a structured ticket** using the format below.

## Output Format

Always output tickets in this structure:

```
🎫 TICKET: [TYPE] <concise, descriptive title>
🔺 PRIORITY: <Critical / High / Medium / Low>
🏷️ TYPE: <Bug / Feature / Improvement / Task / Chore>

📝 DESCRIPTION:
<2–4 sentence summary of the problem or request, written professionally. 
Remove emotional language, informal phrasing, and filler. Keep technical 
details that matter.>

🔄 STEPS TO REPRODUCE:  ← (only for Bug tickets)
1. <Step>
2. <Step>
3. <Step>
4. <Observed result>

✅ ACCEPTANCE CRITERIA:
- <What "done" looks like, written as verifiable statements>
- <One criterion per line>

📌 NOTES / OUT OF SCOPE:
- <Secondary requests, ambiguities, or things intentionally excluded from this ticket>
- <Recommended follow-up tickets if applicable>
```

## Field-by-Field Guidance

### Title
- Format: `[TYPE] Short description of the problem`
- Be specific. Bad: "Fix payment". Good: "Payment button hangs and throws Error 500 on Safari/iOS"
- Max ~80 characters

### Priority
Infer from urgency signals in the briefing:
- **Critical**: Revenue impact, "we're losing money", complete outage, blocking all users
- **High**: Significant user-facing bug, many users affected, time-sensitive
- **Medium**: Partial degradation, affects some users, has a workaround
- **Low**: Cosmetic issue, edge case, nice-to-have

### Type
- **Bug**: Something is broken that used to work (or should work)
- **Feature**: New capability being requested
- **Improvement**: Existing feature that needs enhancement
- **Task / Chore**: Non-code work (copy, config, research, etc.)

### Description
- Rewrite in professional third-person ("Users are unable to..." not "A customer texted me...")
- Preserve all technically relevant details: error codes, device types, browsers, specific UI elements
- Strip: emotional language, urgency filler, personal anecdotes unrelated to the bug

### Steps to Reproduce
- Only include for Bug tickets
- Write from the perspective of a developer trying to reproduce, not the end user's exact story
- Infer reasonable steps from context; note where steps are assumed

### Acceptance Criteria
- Each criterion should be independently verifiable
- Write as present-tense statements: "Payment processes successfully on iOS/Safari"
- Cover: the main fix, absence of the bad behavior, edge cases if mentioned

### Notes / Out of Scope
- Capture secondary requests with a brief recommendation (e.g., "Create a separate low-priority ticket for this")
- Flag any ambiguities the developer should clarify
- Note assumed context (e.g., "Platform assumed to be web; confirm if native app is also affected")

## Multi-Issue Briefings

If the briefing contains **multiple unrelated issues**:
- Create one **primary ticket** for the most critical/urgent issue
- After the primary ticket, add a section: `📋 SUGGESTED ADDITIONAL TICKETS:` listing the other issues as one-line ticket stubs with suggested type and priority, so the user can easily spin them out.

## Tone and Style

- Professional, direct, engineer-friendly
- No emotional language from the original briefing
- Specific and actionable — a developer should be able to start work without asking follow-up questions
- When context is genuinely missing and can't be inferred, add a `❓ OPEN QUESTIONS:` section at the end

## Example

**Input (messy briefing):**
> Hey Fernando, it's John. Listen man, the new checkout page is totally broken. A customer just texted me on Instagram saying they can't pay. They click the green button and it just spins forever and then says 'Error 500'. I think it happens on iPhones mostly, maybe Safari? We need this fixed ASAP, we're losing money! Oh, and by the way, the logo looks a bit too small on that page, can you make it bigger while you're at it? Thanks!

**Output (structured ticket):**
```
🎫 TICKET: [BUG] Checkout page payment button hangs and throws Error 500 on Safari/iOS
🔺 PRIORITY: Critical / High
🏷️ TYPE: Bug

📝 DESCRIPTION:
Users are unable to complete payments on the new checkout page. Clicking the primary 
CTA (green checkout button) results in an infinite loading spinner, followed by a 500 
Internal Server Error.

🔄 STEPS TO REPRODUCE:
1. Navigate to the checkout page using an iOS device (Safari browser).
2. Fill in details and attempt to process a payment.
3. Click the green checkout button.
4. Observe the infinite spinner and the subsequent 500 error.

✅ ACCEPTANCE CRITERIA:
- Payment processes successfully on iOS/Safari.
- No infinite spinner occurs.
- No 500 error is thrown during the checkout flow.

📌 NOTES / OUT OF SCOPE:
- Client also requested increasing the logo size on this page. 
  (Recommendation: Create a separate low-priority design ticket for this to not block the hotfix.)
```
