| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.1 KB |
SKILL.md
View on GitHub---
argument-hint: "<ticket-key-or-url>"
description: Start work on a Jira ticket.
name: start-work
---
# Start Work on a Jira Ticket
Prepare a Liferay ticket for development.
## Resolve the Ticket
Accept a key (`LPD-86295`) or a browse URL from `${ARGUMENTS}`. When nothing is supplied and `${PWD}` matches `*/liferay-portal-<KEY>` where `<KEY>` matches the Jira pattern `[A-Z]+-[0-9]+`, derive the key from the directory name. Otherwise, ask the user.
## Prerequisites
Abort when the working tree has uncommitted changes.
## Determine the Target
Fetch the ticket (issue type, current assignee, subtasks) and resolve the **target** — the ticket where the branch and active work state live:
- **Bug** (`10004`) — the bug itself. There is no child.
- **Story** (`10001`) or **Task** (`10002`) — the **Technical Task** (`10153`) subtask. Jira autocreates it when the parent is moved to an in-progress status, so the target does not exist yet and must be resolved after **Start Work on the Parent**. It may exist from a previous attempt, in which case it becomes the target.
## Start Work on the Parent
Assign the parent to the user and apply the transitions below. When the parent is already in an in-progress status by a different user, refuse to continue.
| Parent Type | Destination | Transition IDs |
| --- | --- | --- |
| Bug | In Progress | `61` |
| Story | In Development | `41`, then `61` |
| Task | In Progress | `21` |
For a Story, apply the two transitions in sequence: `41` moves it to **Ready for Development**, which triggers Jira to autocreate the **Technical Task** subtask, then `61` moves it to **In Development**.
## Start Work on the Child
Skip for **Bug**. For **Story** / **Task**, refetch the parent's subtasks until the **Technical Task** appears, then assign it to the user and transition it:
| Child Type | Destination | Transition ID |
| --- | --- | --- |
| Technical Task | In Progress | `41` |
## Create a Git Branch
Branch off the current HEAD, named after the **target** key. When the branch already exists, check it out instead.
## Make a Plan
Enter plan mode and read the tickets (both parent and child) to make the plan.Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |