Agent Skill · 开发

planning-jira-task（规划 Jira task）

用于处理 Jira 项目、任务、缺陷、Sprint、负责人和状态流转。它适合让 Agent 辅助查询工单、汇总迭代进展、创建任务或整理需求和缺陷信息。使用时要确认项目权限、字段配置和工作流规则，不同团队的 Issue 类型、状态和必填字段可能不同；涉及批量改状态、改负责人或创建工单时，应先预览变更内容再执行。

planning-jira-task 是开发类 Agent Skill，可用宿主为 Codex、Claude、Cursor、Gemini CLI，通过GitHub 仓库获取，权限为只读；许可证信息还不明确，第三方扫描已通过，按安装量在开发类的 21,746 个 Skill 里排第 15,487。

总安装 588周安装 24GitHub Stars 公开资料未说明下载 190核验 2026-05-01

开发只读 GitHub 仓库未标认证来源可访问许可证需确认审计通过 Codex Claude Cursor Gemini CLI

安装说明

本站只整理中文说明，不托管安装包，也不代用户安装。

GitHub

许可证: unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：planning-jira-task（规划 Jira task）
来源仓库：https://github.com/b-mendoza/agent-skills
仓库路径：skills/planning-jira-task
安装命令：
npx skills add https://github.com/b-mendoza/agent-skills --skill planning-jira-task
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/b-mendoza/agent-skills --skill planning-jira-task

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题，一般会读写仓库文件，部分还会执行构建或测试命令。

用于处理 Jira 项目、任务、缺陷、Sprint 和状态流转。适合辅助查询工单、汇总迭代进展、创建任务或整理需求和缺陷信息。使用时需确认项目权限、字段配置和工作流规则，避免格式错误。不同团队的 Issue 类型和必填字段可能不同，需提前适配。批量改状态或负责人时，应先预览变更内容再执行。

来源仓库内路径：skills/planning-jira-task

上手步骤

4 步

1
确认自己的宿主工具
公开资料标注支持 Codex、Claude、Cursor、Gemini CLI；先确认自己用的是其中之一，再按对应工具的 Skills 目录放置。
2
拿到安装命令
可以直接复制的命令是 npx skills add https://github.com/b-mendoza/agent-skills --skill planning-jira-t…；命令里的占位符换成自己的路径或密钥再执行。
3
安装后重启宿主
命令执行完要完全退出宿主工具再打开，让新装的 Skill 被重新扫描到，否则列表里可能看不到。
4
按最小权限试用
它标注为只读，先用只读任务试一次，确认行为符合预期再扩大使用范围。

常见问题

6 条

planning-jira-task 怎么安装？

在终端执行 npx skills add https://github.com/b-mendoza/agent-skills --skill planning-jira-task。装完完全退出宿主工具再打开，让它重新扫描本地 Skill。

planning-jira-task 支持哪些 AI 工具？

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录，一般也能手动放进去，但要自己确认触发方式是否一致。

planning-jira-task 需要什么权限？

权限级别是只读。该 Skill 主要提供规则、说明或参考内容，本身偏只读；真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

planning-jira-task 是免费的吗？

公开资料没有标注明确许可证，收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

planning-jira-task 用的人多吗？

公开数据是累计安装 588 次，近一周安装 24 次，下载 190 次。这些数字来自第三方目录统计，只能当作热度参考，不代表质量或安全性。

planning-jira-task 安全吗？

第三方扫描结果为通过，但这只覆盖已知的静态检查项，不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

同时适配 4 种工具，换客户端不用重新找替代品。
第三方扫描已通过，常见的高风险行为没有命中。
标注为只读权限，试用阶段不容易误改本地文件。

先想清楚的地方

许可证没有明确标注，能不能商用、能不能再分发都不确定。
第三方目录整理，版本更新和行为细节以来源仓库为准。

适不适合你

更适合

已经在用 Codex，想直接扩展它能力的人。
需要处理开发类任务、又不想每次都手写提示词的人。
只想先试试效果、不希望它改动本地文件的人。

不太适合

需要明确授权才能用到公司项目里的场景。
需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类

Skill	总安装	GitHub 星	权限	许可证	扫描
skill-vetter 技能审查员 · OpenClaw	8,779,018	986	操作浏览器	MIT-0	通过
ontology 本体论 · OpenClaw	6,636,960	576	只读	MIT-0	通过
entra-app-registration 内部应用程序注册 · Codex、Claude	6,631,872	764	接触敏感数据	未明确	通过
entra-app-registration 内部应用程序注册 · Codex、Claude	3,757,680	201	接触敏感数据	未明确	通过
nano-banana-pro 纳米香蕉专业版 · OpenClaw	3,526,898	364	接触敏感数据	MIT-0	有提醒
planning-jira-task 规划 Jira task · 本页	588	—	只读	未明确	通过

按安装量取同分类前几名；数字来自第三方目录统计，只作热度参考，不代表质量结论。

SKILL.md 原文

Planning Jira Task

Plan exactly how to execute one task from the task plan for a Jira ticket. This orchestrator does three things: think (interpret summaries and plan state), decide (choose the next planning dispatch or re-plan path), and dispatch (hand execution-heavy work to co-located subagents). The planning artifacts live on disk; the orchestrator keeps only concise summaries in context.

Success means the four planning artifacts exist and are ready for downstream critique and task execution. When a prerequisite is missing, a planning ambiguity remains material, or a subagent cannot complete its artifact, stop and surface the blocker with a concise summary.

Inputs

Input	Required	Example
`TICKET_KEY`	Yes	`JNS-6065`
`TASK_NUMBER`	Yes	`3`
`RE_PLAN`	No	`true`
`DECISIONS_FILE`	No	`docs/JNS-6065-task-3-decisions.md`

Read ./references/data-contracts.md when you need the upstream prerequisites or downstream artifact expectations.

Use RE_PLAN and DECISIONS_FILE only for critique-driven reruns. Read ./references/pipeline.md when deciding which stages to rerun.

Pipeline Stages

execution-prepper validates the task and writes the execution brief.
execution-planner inspects the codebase and writes the execution plan.
test-strategist writes the behavior-driven test specification.
refactoring-advisor writes the refactoring recommendation.
The skill returns only a concise planning summary and the artifact paths needed for downstream critique and task execution.

Subagent Registry

Subagent	Path	Purpose
`execution-prepper`	`./subagents/execution-prepper.md`	Validate task readiness and assemble the execution brief
`execution-planner`	`./subagents/execution-planner.md`	Inspect the codebase and write the implementation plan
`test-strategist`	`./subagents/test-strategist.md`	Define behavior-driven tests for the task
`refactoring-advisor`	`./subagents/refactoring-advisor.md`	Recommend only the refactoring needed for this task

Read a subagent definition only when you are about to dispatch that subagent.

Output Contract

This skill writes only workflow-planning artifacts that capture planning state for this task:

Artifact	Produced by	Consumed by
`docs/<TICKET_KEY>-task-<TASK_NUMBER>-brief.md`	`execution-prepper`	All downstream planning subagents, downstream critique, task execution
`docs/<TICKET_KEY>-task-<TASK_NUMBER>-execution-plan.md`	`execution-planner`	Downstream critique, task execution
`docs/<TICKET_KEY>-task-<TASK_NUMBER>-test-spec.md`	`test-strategist`	Downstream critique, task execution
`docs/<TICKET_KEY>-task-<TASK_NUMBER>-refactoring-plan.md`	`refactoring-advisor`	Downstream critique, task execution

On a successful run, all four files exist. On a re-plan, overwrite only the files owned by the subagents that are re-run. These workflow-state documents stay on disk for the life of the workflow and are never committed to git.

Dispatch Rules

Read ./references/data-contracts.md when checking prerequisites or artifact expectations.
Read ./references/pipeline.md when running the standard planning pipeline or a critique-driven re-plan.
At each boundary, validate that the current required input exists before dispatch: the task plan and task section for execution-prepper, then the prior-stage artifacts for later subagents. Confirm that the expected output artifact was written before advancing.
Pass only the explicit handoffs required for the current stage: task identity inputs for execution-prepper, plus RE_PLAN and DECISIONS_FILE on critique-driven reruns; then prior-stage artifact paths and DECISIONS_FILE when applicable for later stages.
Keep only verdicts, file paths, and next-step-relevant notes from each subagent.
Advance sequentially. Rerun only the subagents invalidated by critique, plus their downstream dependents.
Surface blockers and pause for resolution when ambiguity remains.

Reference Guide

This table tells you which reference to load. ## Orchestration Steps remains the source of truth for the actual pipeline order.

Situation	Reference file	Purpose
Standard planning run	`./references/pipeline.md`	Dispatch order, handoffs, and success criteria
Re-plan after critique	`./references/pipeline.md`	Targeted rerun rules and retry limit
Contract questions	`./references/data-contracts.md`	Upstream prerequisites and downstream consumers

Orchestration Steps

Read ./references/data-contracts.md and confirm the task-plan prerequisites exist for TICKET_KEY and TASK_NUMBER.
Read ./references/pipeline.md.
Use ./references/pipeline.md to determine the next required subagent. On a standard run, start with execution-prepper. On a critique-driven re-plan, start at the earliest invalidated stage. Pass only that subagent's required explicit inputs. For execution-prepper, pass only TICKET_KEY, TASK_NUMBER, and when applicable RE_PLAN and DECISIONS_FILE. For later stages, pass the artifact file paths required by ./references/pipeline.md.
Retain only its verdict, artifact path, and the notes needed for the next decision.
Continue until all required planning artifacts are written and confirmed, or a blocker is surfaced.
Report completion with the task number and title, all four artifact paths, one or two sentences on the recommended approach, the number or shape of tests specified, and the refactoring verdict.

Example

Dispatch execution-prepper with TICKET_KEY, TASK_NUMBER
Subagent returns: PREP: PASS Brief: docs/JNS-6065-task-2-brief.md
Dispatch execution-planner with BRIEF_FILE=docs/JNS-6065-task-2-brief.md
Subagent returns: PLAN: PASS Execution plan: docs/JNS-6065-task-2-execution-plan.md
Dispatch test-strategist with BRIEF_FILE=docs/JNS-6065-task-2-brief.md and PLAN_FILE=docs/JNS-6065-task-2-execution-plan.md
Subagent returns: TEST_SPEC: PASS Spec: docs/JNS-6065-task-2-test-spec.md
Dispatch refactoring-advisor with BRIEF_FILE=docs/JNS-6065-task-2-brief.md, PLAN_FILE=docs/JNS-6065-task-2-execution-plan.md, and TEST_SPEC_FILE=docs/JNS-6065-task-2-test-spec.md
Subagent returns: REFACTORING: PASS Refactoring plan: docs/JNS-6065-task-2-refactoring-plan.md
Tell the user: "Task 2 - Add webhook retry handling planning complete. Artifacts: brief, execution plan, test spec, and refactoring plan written. Recommended approach: add retry orchestration in the webhook service, then thread retry state through the worker path. Tests: 3 behavior groups with 6 high-priority checks. Refactoring verdict: Refactor during implementation."

The orchestrator keeps only those summaries and the artifact paths.

平台分布

Codex

36.15%

按下载量换算69

Claude

30.39%

按下载量换算58

Cursor

19.36%

按下载量换算37

Gemini CLI

10.28%

按下载量换算20

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容，本身偏只读；真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源，建议同时核对源仓库。

继续浏览同类 Skills

更多开发 Skills（21,746）返回 Skills 目录

上一个 Skill

planning-github-task（规划 GitHub task）

b-mendoza/agent-skills

用于围绕 GitHub 仓库、Issue、Pull Request、分支、提交和代码协作流程提供辅助能力。它适合让 Agent 查询项目状态、整理变更、辅助创建或检查协作事项，并把仓库中的信息转成可执行的下一步。使用时需要区分只读查询和写入操作；涉及创建 PR、修改 Issue、推送分支或访问私有仓库时，应确认 token 权限、目标仓库范围和用户授权。

下一个 Skill

plannotator（plannotator 命令行）

supercent-io/skills-template

plannotator 用于处理浏览器自动化、网页检查和页面信息提取，适合在 Codex、Claude、Cursor、Gemini CLI 中需要让 Agent 打开页面、读取网页或验证前端流程时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。