jpskill.com
💼 ビジネス コミュニティ

creating-jira-subtasks

Creates or reconciles Jira subtasks for an approved Phase 4 task plan. Use after docs/<TICKET_KEY>-tasks.md is clarified and the user has approved Jira writes; dispatches subtask-creator and returns a compact status summary.

⚡ おすすめ: コマンド1行でインストール(60秒)

下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。

🍎 Mac / 🐧 Linux 
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o creating-jira-subtasks.zip https://jpskill.com/download/23417.zip && unzip -o creating-jira-subtasks.zip && rm creating-jira-subtasks.zip
🪟 Windows (PowerShell) 
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/23417.zip -OutFile "$d\creating-jira-subtasks.zip"; Expand-Archive "$d\creating-jira-subtasks.zip" -DestinationPath $d -Force; ri "$d\creating-jira-subtasks.zip"

完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。

💾 手動でダウンロードしたい(コマンドが難しい人向け)
  1. 1. 下の青いボタンを押して creating-jira-subtasks.zip をダウンロード
  2. 2. ZIPファイルをダブルクリックで解凍 → creating-jira-subtasks フォルダができる
  3. 3. そのフォルダを C:\Users\あなたの名前\.claude\skills\(Win)または ~/.claude/skills/(Mac)へ移動
  4. 4. Claude Code を再起動
⬇ .zip でダウンロード(推奨) ⬇ .skill 形式(上級者用) 元のソース ↗

⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。

🎯 このSkillでできること

下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。

📦 インストール方法 (3ステップ)

  1. 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
  2. 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
  3. 3. 展開してできたフォルダを、ホームフォルダの .claude/skills/ に置く
    • · macOS / Linux: ~/.claude/skills/
    • · Windows: %USERPROFILE%\.claude\skills\

Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。

詳しい使い方ガイドを見る →
最終更新
2026-05-18
取得日時
2026-05-18
同梱ファイル
4
📖 Claude が読む原文 SKILL.md(中身を展開)

この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。

Creating Jira Subtasks

You are a Phase 4 Jira subtask orchestrator. The orchestrator does three things: derive identifiers from JIRA_URL, dispatch subtask-creator with the original URL, and relay the structured Phase 4 summary to the caller.

The subagent owns plan parsing, Jira operations, plan-file edits, and validation. The orchestrator keeps only verdicts, paths, counts, warnings, and failures.

Inputs

Input Required Example
JIRA_URL Yes https://workspace.atlassian.net/browse/PROJ-123

Derive locally for routing and reporting only. The full URL is the canonical context that flows to the subagent and to Jira-capable tools:

  • Workspace: subdomain before .atlassian.net
  • Project: prefix before the dash in the ticket key
  • TICKET_KEY: full path segment, such as PROJ-123

Progressive Loading Map

Read each row's target file only when the listed need arises. Load paths are relative to this SKILL.md; never preload them.

Need Load
Phase 4 artifact shape, summary fields, or status semantics ./references/phase-4-io-contracts.md
Current Jira REST v3 syntax, subtask configuration, Atlassian Document Format, or skill-maintenance rationale ./references/external-sources.md, then fetch only the smallest relevant URL
Subtask creation or reconciliation ./subagents/subtask-creator.md

External URLs are optional, just-in-time sources. This skill remains executable from its bundled files when network access is unavailable; the subagent and references include enough local guidance for routine runs.

Subagent Registry

Read a subagent definition only when dispatching that subagent.

Subagent Path Purpose
subtask-creator ./subagents/subtask-creator.md Reconciles the clarified plan with Jira subtasks and returns the Phase 4 summary

Workflow

  1. Confirm JIRA_URL is present and derive TICKET_KEY for local reporting.
  2. Read ./references/phase-4-io-contracts.md only when interpreting an output, validating Phase 4, or explaining the required artifact shape.
  3. Read ./subagents/subtask-creator.md and dispatch it with JIRA_URL.
  4. Route on the returned SUBTASKS and Validation lines.
  5. Report a concise Phase 4 rollup: parent, TICKET_KEY, plan path, counts, warnings, failures, and the reminder that implementation work has not begun.

Routing Rules

Result Orchestrator action
SUBTASKS: PASS with Validation: PASS Report success and proceed
SUBTASKS: WARN with Validation: PASS Report usable output with visible warnings or failed task links
SUBTASKS: BLOCKED Stop and surface the plan-shape or unsafe-linkage issue
SUBTASKS: FAIL Stop and surface the fatal Jira or validation failure
SUBTASKS: ERROR or Validation: FAIL Stop and surface the unexpected failure or local contract failure

Treat Validation: NOT_RUN as incomplete Phase 4 output even when the top-level status is already BLOCKED, FAIL, or ERROR.

Output Contract

Return only the subagent's structured summary plus a short caller-facing rollup. The full summary schema lives in ./references/phase-4-io-contracts.md.

Do not add GitHub-style write-model or capability lines to the Jira report. Jira uses one native subtask relationship path for this workflow.

Example

<example> Input: JIRA_URL=https://workspace.atlassian.net/browse/PROJ-123

  1. The orchestrator derives TICKET_KEY=PROJ-123 for reporting.
  2. The orchestrator dispatches subtask-creator with JIRA_URL.
  3. The subagent returns the contract summary with SUBTASKS: PASS, Validation: PASS, parent, plan path, counts, warnings, and failures.
  4. The orchestrator reports success, creation/link counts, warnings/failures if any, and that no implementation has started. </example>

同梱ファイル

※ ZIPに含まれるファイル一覧。`SKILL.md` 本体に加え、参考資料・サンプル・スクリプトが入っている場合があります。