creating-jira-subtasks
Creates or reconciles Jira subtasks for an approved Phase 4 task plan. Use after docs/ -tasks.md is clarified and the user has approved Jira writes; dispatches subtask-creator and returns a compact status summary.
- Installs
- 53
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/b-mendoza/agent-skills --skill creating-jira-subtasks- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads creating-jira-subtasks automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.
Run this skill only after the caller or user has approved Jira subtask writes
and the scoped update to docs/<TICKET_KEY>-tasks.md. Normal orchestration
passes that approval as APPROVED_MUTATION_SCOPE. If invoked directly and
approval is unclear, ask once for that approval; if approval is absent or
declined, return the contract-defined blocked summary with
Validation: NOT_RUN.
Inputs
| Input | Required | Example |
|---|---|---|
JIRA_URL | Yes | https://workspace.atlassian.net/browse/PROJ-123 |
APPROVED_MUTATION_SCOPE | No | Jira subtasks plus docs/PROJ-123-tasks.md update approved |
Normal orchestrated runs include APPROVED_MUTATION_SCOPE. Direct standalone
runs may collect the same approval from the user before dispatch. 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
- Confirm
JIRA_URLis present. If it is missing or malformed, return the blocked summary from./references/phase-4-io-contracts.mdwithParent: UNKNOWN,TICKET_KEY: UNKNOWN,Plan file: not updated, zero counts, andValidation: NOT_RUN. - Derive
TICKET_KEYfor local reporting, then confirm the run is approved for Jira writes plus the scoped plan-file update. If approval is absent or declined, return the same blocked-summary shape with the derivedTICKET_KEYandPlan file: not updated. - Read
./references/phase-4-io-contracts.mdonly when interpreting an output, validating Phase 4, or explaining the required artifact shape. - Read
./subagents/subtask-creator.mdand dispatch it withJIRA_URLand the approved mutation scope. The approved scope is limited to Jira subtask create/reuse actions anddocs/<TICKET_KEY>-tasks.md. - Route on the returned
SUBTASKSandValidationlines. - 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 linked output, visible warnings, and any Not Created rows that require manual resolution before that task can execute |
SUBTASKS: BLOCKED | Stop and surface missing approval, unsafe plan shape, unsafe linkage, or manual subtask-type selection |
SUBTASKS: FAIL | Stop and surface the fatal Jira, configuration, required-field, 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`- The orchestrator derives
TICKET_KEY=PROJ-123for reporting. - The orchestrator dispatches
subtask-creatorwithJIRA_URLand approved mutation scope. - The subagent returns the contract summary with
SUBTASKS: PASS,Validation: PASS, parent, plan path, counts, warnings, and failures. - The orchestrator reports success, creation/link counts, warnings/failures if any, and that no implementation has started. </example>
FAQ
What does the creating-jira-subtasks skill do?
Creates or reconciles Jira subtasks for an approved Phase 4 task plan. Use after docs/ -tasks.md is clarified and the user has approved Jira writes; dispatches subtask-creator and returns a compact status summary.
How do I install creating-jira-subtasks?
Run npx skills add https://github.com/b-mendoza/agent-skills --skill creating-jira-subtasks in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/creating-jira-subtasks/ (personal) or .claude/skills/creating-jira-subtasks/ (project).
Which AI agents can use creating-jira-subtasks?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is creating-jira-subtasks safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains creating-jira-subtasks?
It is published by b-mendoza in b-mendoza/agent-skills. It has 53 recorded installs.
More from b-mendoza/agent-skills
validate-implementation-plan
b-mendoza/agent-skills
Audits an implementation plan for requirements traceability, avoidable complexity, risky assumptions, and evidence gaps. Use when reviewing an AI-generated or human-authored plan, design proposal, implementation outline, task breakdown, or architecture plan and the user wants a standalone audit report without overwriting the source plan.
recency-guard
b-mendoza/agent-skills
Validates answers that depend on current external facts, including prices, versions, policies, rankings, recommendations, documentation, and availability. Use when the user asks for current, latest, verified, fact-checked, or up-to-date answers. Coordinates recency-checker and claim-verifier subagents to produce a current, qualified final answer.
pr-creator
b-mendoza/agent-skills
Create review-ready pull requests or merge requests from the current branch through a fork-aware, idempotent, preview-first, user-approved workflow. Use when the user asks to create, open, draft, or submit a PR, pull request, merge request, or code review request, or says their branch is ready for review.
review-pull-request
b-mendoza/agent-skills
Reviews one GitHub pull request and prepares a verified local review or posts its exact approved contents. Use when the user asks to review a PR, audit a pull request, draft review comments or request-changes feedback, write a PR review file, or optionally post approved review comments. Handles exactly one PR. Does not open pull requests, fix reviewed code, implement incoming review feedback, or resume saved reviews.
committing-scoped-changes
b-mendoza/agent-skills
Open the skill to read its SKILL.md instructions.
responding-to-pr-review-comments
b-mendoza/agent-skills
Open the skill to read its SKILL.md instructions.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。