Token导航 LogoToken导航TokenDH.com
中转站排行榜
开发只读github未标认证来源可访问许可证需确认审计通过

planning-jira-task（规划 Jira task）

Agent Skill

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

总安装

588

周安装

24

GitHub Stars

公开资料未说明

下载量

190
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

用于处理 Jira 项目、任务、缺陷、Sprint 和状态流转。

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

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

InputRequiredExample
TICKET_KEYYesJNS-6065
TASK_NUMBERYes3
RE_PLANNotrue
DECISIONS_FILENodocs/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

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

Subagent Registry

SubagentPathPurpose
execution-prepper./subagents/execution-prepper.mdValidate task readiness and assemble the execution brief
execution-planner./subagents/execution-planner.mdInspect the codebase and write the implementation plan
test-strategist./subagents/test-strategist.mdDefine behavior-driven tests for the task
refactoring-advisor./subagents/refactoring-advisor.mdRecommend 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:

ArtifactProduced byConsumed by
docs/<TICKET_KEY>-task-<TASK_NUMBER>-brief.mdexecution-prepperAll downstream planning subagents, downstream critique, task execution
docs/<TICKET_KEY>-task-<TASK_NUMBER>-execution-plan.mdexecution-plannerDownstream critique, task execution
docs/<TICKET_KEY>-task-<TASK_NUMBER>-test-spec.mdtest-strategistDownstream critique, task execution
docs/<TICKET_KEY>-task-<TASK_NUMBER>-refactoring-plan.mdrefactoring-advisorDownstream 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.

SituationReference filePurpose
Standard planning run./references/pipeline.mdDispatch order, handoffs, and success criteria
Re-plan after critique./references/pipeline.mdTargeted rerun rules and retry limit
Contract questions./references/data-contracts.mdUpstream prerequisites and downstream consumers

Orchestration Steps

  1. Read ./references/data-contracts.md and confirm the task-plan prerequisites exist for TICKET_KEY and TASK_NUMBER.
  2. Read ./references/pipeline.md.
  3. 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.
  4. Retain only its verdict, artifact path, and the notes needed for the next decision.
  5. Continue until all required planning artifacts are written and confirmed, or a blocker is surfaced.
  6. 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

  1. Dispatch execution-prepper with TICKET_KEY, TASK_NUMBER
  2. Subagent returns: PREP: PASS Brief: docs/JNS-6065-task-2-brief.md
  3. Dispatch execution-planner with BRIEF_FILE=docs/JNS-6065-task-2-brief.md
  4. Subagent returns: PLAN: PASS Execution plan: docs/JNS-6065-task-2-execution-plan.md
  5. Dispatch test-strategist with BRIEF_FILE=docs/JNS-6065-task-2-brief.md and PLAN_FILE=docs/JNS-6065-task-2-execution-plan.md
  6. Subagent returns: TEST_SPEC: PASS Spec: docs/JNS-6065-task-2-test-spec.md
  7. 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
  8. Subagent returns: REFACTORING: PASS Refactoring plan: docs/JNS-6065-task-2-refactoring-plan.md
  9. 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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

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 的任务。

安装前确认

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

来源信息

GitHub 仓库

github.com

/b-mendoza/agent-skills

SKILL.md 来源

github.com

/b-mendoza/agent-skills/tree/main/skills/planning-jira-task

skills-sh

skills.sh

/b-mendoza/agent-skills/planning-jira-task

继续浏览同类 Skills

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

上一个 Skill

planning-github-task（规划 GitHub task）

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

下一个 Skill

plannotator（plannotator 命令行）

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