planning-jira-tasks
Phase 2 of the Jira planning workflow. Reads a Jira ticket snapshot, dispatches a plan/prioritize/validate pipeline, and writes docs/ -tasks.md with branch names for every planned Jira subtask.
- Installs
- 55
- 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 planning-jira-tasks- 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 planning-jira-tasks 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.
Planning Jira Ticket Tasks
Plan a Jira ticket snapshot into docs/<TICKET_KEY>-tasks.md. This is the
Phase 2 orchestrator for the Jira planning workflow: it routes stages,
dispatches specialists, preserves stage artifacts for resume and critique, and
returns a concise handoff.
The orchestrator keeps only workflow state, subagent verdicts, paths, counts, and user decisions in context. Detailed contracts, templates, validation checks, and source-backed background are loaded just in time from bundled references or optional external URLs.
Inputs
| Input | Required | Example |
|---|---|---|
TICKET_KEY | Yes | JNS-6065 |
RE_PLAN | No | true |
DECISIONS | No | SSO decision changes task dependencies |
Phase 2 is file-driven. docs/<TICKET_KEY>.md must already exist as the Jira
ticket snapshot.
Progressive Loading Map
| Need | Load |
|---|---|
| Normal run, dispatch payloads, retry loop | ./references/execution-guide.md |
| Final artifact contract, branch policy, subtask handling | ./references/output-contract.md |
| Critique-driven re-plan or recovery from stage artifacts | ./references/re-plan-cycle.md |
| Source-backed background or current platform syntax | ./references/external-sources.md |
| Subagent-specific guides, templates, or validation checks | Load only from the dispatched subagent |
Bundled paths in this file are relative to this SKILL.md; files loaded later
use paths relative to their own locations. All bundled files travel with the
package.
External URLs are optional progressive enhancement: fetch them only when local
contracts need background or current syntax, and proceed from bundled references
when network access is unavailable.
Subagent Registry
| Subagent | Path | Purpose |
|---|---|---|
task-planner | ./subagents/task-planner.md | Decompose the ticket and draft the stage 1 plan |
dependency-prioritizer | ./subagents/dependency-prioritizer.md | Add dependency order, priority, and branch names |
task-validator | ./subagents/task-validator.md | Validate the prioritized plan and append QA findings |
stage-validator | ./subagents/stage-validator.md | Check preflight, inter-stage, and final structural gates |
Workflow
| Path | When | Next reference |
|---|---|---|
| Normal | RE_PLAN is absent or false | ./references/execution-guide.md |
| Re-plan | RE_PLAN=true with critique decisions | ./references/re-plan-cycle.md, then ./references/execution-guide.md |
The normal path is: preflight snapshot validation, Stage 1 detailed planning, Stage 1 validation, Stage 2 dependency/branch planning, Stage 2 validation, Stage 3 final validation report, Stage 3 validation, postpipeline validation, handoff.
Preserve docs/<TICKET_KEY>-stage-1-detailed.md,
docs/<TICKET_KEY>-stage-2-prioritized.md, and
docs/<TICKET_KEY>-tasks.md on disk. They are orchestration state for resume,
critique, and targeted retries; they are not implementation outputs.
Use targeted fix loops only. Re-dispatch the stage that produced the failing artifact, pass only the validator's issue list, rerun only the failing gate, and stop after 3 failed cycles for the same gate.
Return Format
Return only this phase handoff. Use PLANNING: PASS only when every stage and
stage-validation gate has passed.
PLANNING: PASS | FAIL
TICKET_KEY: <TICKET_KEY>
File: <final file path or "not written">
Tasks: <N>
Branches: <N unique branch names>
Cross-cutting questions: <N>
Validation warnings: <N>
Failure category: PREFLIGHT | STAGE_1 | STAGE_2 | STAGE_3 | POSTPIPELINE | NONE
Reason: <one line>
Artifacts preserved: <comma-separated paths>
Example
<example> Input: `TICKET_KEY=JNS-6065`- Load
./references/execution-guide.mdfor the dispatch payloads. - Dispatch
stage-validatorforpreflight; it returnsSTAGE_VALIDATION: PASS. - Dispatch
task-planner,dependency-prioritizer, andtask-validatorin sequence, validating after each produced artifact. - Dispatch
stage-validatorforpostpipeline; it returnsSTAGE_VALIDATION: PASS. - Return the concise
PLANNING: PASShandoff with preserved artifact paths. </example>
FAQ
What does the planning-jira-tasks skill do?
Phase 2 of the Jira planning workflow. Reads a Jira ticket snapshot, dispatches a plan/prioritize/validate pipeline, and writes docs/ -tasks.md with branch names for every planned Jira subtask.
How do I install planning-jira-tasks?
Run npx skills add https://github.com/b-mendoza/agent-skills --skill planning-jira-tasks 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/planning-jira-tasks/ (personal) or .claude/skills/planning-jira-tasks/ (project).
Which AI agents can use planning-jira-tasks?
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 planning-jira-tasks 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 planning-jira-tasks?
It is published by b-mendoza in b-mendoza/agent-skills. It has 55 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 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。