메뉴
Fetches a JIRA ticket by key or URL and extracts structured requirements including summary, description, acceptance criteria, subtasks, labels, and priority. Use when given a JIRA ticket link, ticket key, or asked to read/interpret a ticket.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | read-jira-ticket |
| description | Fetches a JIRA ticket by key or URL and extracts structured requirements including summary, description, acceptance criteria, subtasks, labels, and priority. Use when given a JIRA ticket link, ticket key, or asked to read/interpret a ticket. |
| argument-hint | JIRA ticket key (e.g., PROJ-123) or full URL |
Fetches a JIRA ticket and produces a structured requirements document that downstream agents can use for planning and implementation.
PROJ-123) or URLThe following environment variables must be set:
JIRA_BASE_URL — Base URL of the JIRA instanceJIRA_API_TOKEN — API token for authenticationJIRA_EMAIL — Email associated with the API tokenRun the fetch script to retrieve the ticket:
python3 ./.github/skills/read-jira-ticket/scripts/fetch_jira.py <TICKET_KEY_OR_URL>
Reference: fetch_jira.py
Parse the JSON output and extract these sections:
Produce a structured requirements document with the following format:
## Ticket: <KEY> — <Summary>
**Type:** <issue_type> | **Priority:** <priority> | **Status:** <status>
**Labels:** <labels> | **Story Points:** <story_points>
### Description
<Cleaned description text>
### Requirements
- <Functional requirement 1>
- <Functional requirement 2>
...
### Acceptance Criteria
- <Criterion 1>
- <Criterion 2>
...
(If no explicit acceptance criteria found, derive them from the description)
### Subtasks
- [ ] <KEY>: <Summary> (<Status>)
...
### Related Issues
- <Relationship type>: <KEY> — <Summary>
...
### Implementation Hints
- <Any technical details, component mentions, or architectural hints from the ticket>
### Additional Notes
- Plan approval required: <Yes/No based on labels or ticket content>
If the script fails:
echo $JIRA_BASE_URL, etc.)python3 --version)PROJ-123 pattern)Creates, reads, and updates the per-workflow agent state file at .github/state/<TICKET-KEY>.md — a fast-access local mirror of workflow context that reduces GitHub API round-trips and enables richer resumption. Use when creating a new workflow, at phase transitions, or when resuming.
Restores full workflow context from an existing draft PR and its state file, then returns the current phase and all parsed context (plan, branch, ticket key, task statuses) so the orchestrator can route to the correct resume point. Use when the input to a workflow is a PR URL or number.
Updates an existing PR body by modifying MUTABLE blocks and appending to APPEND-ONLY blocks. Use when transitioning between workflow phases.
Updates an existing PR body by modifying MUTABLE blocks and appending to APPEND-ONLY blocks. Use when transitioning between workflow phases.
Creates, reads, and updates the per-workflow agent state file at .github/state/<TICKET-KEY>.md — a fast-access local mirror of workflow context that reduces GitHub API round-trips and enables richer resumption. Use when creating a new workflow, at phase transitions, or when resuming.
Creates a draft Pull Request using the canonical PR body template. Populates all initial blocks and returns PR URL + PR number. Use after the branch has been created and pushed.