Terminal
Terminal/Skill
Gives an agent read and write access to Jira work items, boards, sprints, and fields through the TWG command line tool.
By Atlassian
Works with
npx skills add atlassian/twg-cli --skill twg-jiraUse with the root twg skill when Jira is the source of truth or a Jira
mutation is required. This skill owns Jira semantics and safety; command
grammar comes from live twg help.
Run twg <command>. On shell command not found, use $HOME/.local/bin/twg
(macOS/Linux) / $env:LOCALAPPDATA\Programs\twg\bin\twg.exe (PowerShell), then
tell user to add that directory to PATH. Do not treat auth or command errors as
PATH failures.
Do not load this skill merely because Jira appears as one supporting artifact inside a cross-product answer.
| Intent | Route |
|---|---|
| Known workitem | Native workitem get |
| Several known workitems | One get/bulk-get with all keys |
| Jira-only fuzzy text discovery | Workitem search (JQL-backed) |
| Exact Jira filtering | Workitem query with JQL |
| Semantic Jira discovery | rovo search --app jira |
| Duplicate workitem detection | references/duplicates.md |
| Related artifacts or people | Native read plus context |
| Link implementation artifacts | jira workitem link |
| Create or update | Field metadata, then mutation |
| Change workflow state | Discover transitions, then transition |
| Board or sprint ordering | Board/backlog/sprint command |
| Jira configuration | Jira administration namespace |
Run one focused twg help describe "<exact path>" before an unfamiliar or
consequential mutation.
get avoids supplemental hydration; add
--comments and/or --remote-links, or --full for all fields plus both.jira workitem get,
jira workitem bulk-get, and context jira workitem all accept every key at
once. Never loop get over a key list. When the fields are queryable, use
jira workitem query --jql <jql> --fields <fields> and skip hydration.customfield_* IDs rather than display names in writes.twg jira workitem transition --id <KEY> --site <SITE> -o json without --transition-id to discover available transitions and their required screen fields.requirements to gather field values before calling with --transition-id.Won't Do, Declined, Duplicate, or another Resolution.twg-context-discovery for dependencies, related documents, or
implementation links; twg-responsibility-routing for owners, experts,
authority, or escalation.twg-status-rollups for project, sprint, team, or leadership synthesis.twg-engineering-work when the Jira anchor must be traced to PRs or
repositories.twg-operational-health for incident, PIR, or reliability workflows.references/workitems.md - workitem reads, writes, comments, and linksreferences/fields-and-transitions.md - metadata-first fields and workflow changesreferences/querying.md - JQL and board/backlog selectionreferences/duplicates.md - prompt driven duplicate detection and reviewreferences/rich-content.md - descriptions, comments, and mentionsreferences/administration.md - Jira configuration versus workitem data