Skip to content

LedgerHQ/lumen / .claude/skills/jira-ticket

jira-ticket

Verified

Use when creating or drafting DLS (Lumen team) Jira tickets: a bug, a task, or an epic broken down from a tab of the Lumen scope spreadsheet. Holds the DLS project conventions (title prefix, issue types, epics, labels) and the ticket templates. Also the source of truth for finding the current sprint's tickets.

FileKindSize
SKILL.mdskill md3.7 KB
references/templates.mdmarkdown967 B
---
name: jira-ticket
description: >-
  Use when creating or drafting DLS (Lumen team) Jira tickets: a bug, a task,
  or an epic broken down from a tab of the Lumen scope spreadsheet. Holds the
  DLS project conventions (title prefix, issue types, epics, labels) and the
  ticket templates. Also the source of truth for finding the current sprint's
  tickets.
---

# Jira ticket (DLS)

Project `DLS`, board 3464:
https://ledgerhq.atlassian.net/jira/software/c/projects/DLS/boards/3464/backlog.
Use the Atlassian MCP.

## Title

`<prefix> <Component>: <what>`, e.g. `[M][D] Table: add show-more row`.

| Prefix | Scope |
|---|---|
| `[D]` | Desktop/web: `libs/ui-react` |
| `[M]` | Mobile: `libs/ui-rnative` |
| `[M][D]` | Both platforms |
| none | Tech task or other (tokens, tooling, CI, docs) |

The prefix order is always `[M][D]`, with no colon. Epics use `[LUMEN] <name>`.

## Type, epic, labels

- **Type**: `Bug` for something broken, `Task` for everything else, `Epic`
  for a project scope.
- **Epic** (parent): the project epic if there is one. Otherwise the current
  PI bucket: Bug → `[LUMEN] Run <PI>`, no prefix → `[LUMEN] Tech tasks <PI>`,
  `[D]`/`[M]` → `[LUMEN] functional tasks <PI>`. Bucket epics for
  several PIs stay open at once, so status doesn't tell the current one: take
  the PI of the bucket epics that the last two weeks' tickets were filed under
  (`project = DLS AND created >= -14d`, read their parent), and show it in the
  draft so the user confirms it.
- **Labels**: `tech_DLS`, plus `LUMEN_TO_REFINE` unless the ticket is ready
  to be picked up.
- **Epics** also set Dream Team (`customfield_10332`) = Lumen Team.
- Leave sprint and priority empty unless the user gives them. Assign the
  ticket to the user when they'll work on it: the `open-pr` lookup below only
  finds tickets assigned to them.

## Body

Use the template for the type in [references/templates.md](references/templates.md).
Fill what you know, delete the sections that don't apply, and never invent
repro steps or acceptance criteria. Ask instead.

## From the scope spreadsheet

One bottom tab = one project scope. Ask for the sheet link and tab if they
aren't given; read it with the Google Sheets or Drive MCP. Create one Epic for
the tab, then go through its rows (one row = one component).

Column positions vary between tabs, so find them by header name. The dev
columns that matter are **Lumen - React** (`[D]`) and **Lumen - React Native**
(`[M]`); **Lumen - Figma** is design work and never makes a dev ticket. Each
cell holds a status:

Only cells marked **To Create** get a ticket (`<Component>: create`). Every
other status (Available, Update Needed, Out of Scope, To Discuss, Ticket
Created) gets none; list To Discuss rows in the draft as open questions.

When both dev columns are To Create, create one `[M][D]` task, or split it into
`[D]` and `[M]` tasks when the platforms ship separately. Put the Comment
column and any Figma or Jira design-ticket link in the task's Context.

Once the tickets exist, write back to the sheet with the Google Sheets MCP
(`update_values`): set each cell that produced a ticket to **Ticket Created**,
and put the ticket key in the tab's Ticket column when it has one. Re-read each
cell first and only change it if it still says To Create. Without write access,
skip this step.

## Create

Creating tickets is visible to the whole team: show the drafts (title, type,
epic, labels, body) and create only after the user confirms. For a
spreadsheet breakdown, confirm the whole list once. Reply with the keys and
links.

## Current sprint lookup

For "which ticket is this?" (used by the `open-pr` skill):
`project = DLS AND sprint in openSprints() AND assignee = currentUser() ORDER BY updated DESC`.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall