メニュー
Use when querying or automating Jira - sprints, issues, epics, stories, boards, or correlating Jira data with external systems
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when querying or automating Jira - sprints, issues, epics, stories, boards, or correlating Jira data with external systems
Based on our current conversion write a document with high level user stories representing the valuable increments the work can be split into
Grilling session for MBM that challenges a plan against the existing domain model, sharpens terminology using UBIQUITOUS_LANGUAGE.md, and updates MBM docs/KDRs as decisions crystallise. Use when the user wants to stress-test a plan against MBM's language and documented decisions.
Use the `mdc` CLI to publish local Markdown files to Confluence and fetch/pull Confluence pages back into Markdown files. Use when the user asks to publish, update, sync, pull, fetch, or create Confluence pages from markdown, including shorthand like "Publish this KDR".
Use the local Playwright browser tools to browse websites, navigate pages, extract visible text or HTML, take screenshots, and fill simple forms. Use when the user asks to inspect a live website, click through a flow, capture a screenshot, or read content that requires a real browser.
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
| name | jira-cli |
| description | Use when querying or automating Jira - sprints, issues, epics, stories, boards, or correlating Jira data with external systems |
CRITICAL: You MUST use the Task tool with
subagent_type: "general"to execute Jira CLI commands. NEVER runjiracommands directly in your bash session.
Example Task invocation:
Task(subagent_type="general", prompt="Use jira CLI to list current sprint issues: jira sprint list --current --plain")
This preserves conversation context and isolates CLI output.
Command-line interface for Jira. Always use --plain flag when available for scriptable, parseable output.
Primary project: MDBIM. Override with -p PROJECT for other projects.
| Task | Command |
|---|---|
| List my issues | jira issue list -a$(jira me) --plain |
| View issue | jira issue view ISSUE-KEY --plain |
| Create issue | jira issue create -tTask -s"Summary" --no-input |
| Edit issue | jira issue edit ISSUE-KEY -s"New summary" |
| Move/transition | jira issue move ISSUE-KEY "In Progress" |
| Assign issue | jira issue assign ISSUE-KEY $(jira me) |
| Current sprint | jira sprint list --current --plain |
| List epics | jira epic list --plain |
| Open in browser | jira open ISSUE-KEY |
| Who am I | jira me |
For detailed flags and examples, see issue-commands.md, sprint-commands.md, epic-commands.md, and other-commands.md in this skill directory.
| Flag | Description |
|---|---|
-p, --project | Project key (default: configured project) |
-c, --config | Config file path |
--debug | Enable debug output |
-h, --help | Help for any command |
--plain)| Flag | Description |
|---|---|
--plain | Plain text output (use this!) |
--no-headers | Hide table headers (with --plain) |
--no-truncate | Show all columns (with --plain) |
--columns | Select columns to display |
--raw | Raw JSON output |
--csv | CSV format output |
For board, project, release, and shell completion commands, see other-commands.md in this skill directory. utat