Results for “ticket-creation”

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

Break a work-items.md file (produced by /plan-work-items) into independently-grabbable Jira tickets, one per slice, in a single Jira project. Use when you want to turn a work-items file into Jira tickets, publish work items as Jira issues, or create implementation tickets that can be worked on and tracked in Jira. Requires a configured Atlassian MCP server. Does not produce the work-items file itself — use plan-work-items to break a plan into work items first. Does not post to GitHub — use work-items-to-issues for GitHub issues.

ガイド・教科書・チートシート・語彙帳・チュートリアル作成の最初の入り口（ディスパッチャ）。内容から「読む系（詳細ガイド）」「引く系（チートシート/語彙帳）」をLLMが判定し、確認後に guide-builder か textbook-guide に分岐。ユーザーは種別を覚えなくてよい。 「ガイド作って」「教科書作って」「チートシート作って」「語彙帳作って」「チュートリアル作って」「/make-guide」で発火。

在 AI 编程工作流中直接检索、分析和更新 Jira 工单。支持 MCP（推荐）和直接 REST API 两种方式。

Plan a chunk of work too big for one agent session by putting it on a shared whiteboard — a map of investigation tickets on GitHub Issues — working them until nothing is left to decide, then snapshotting the board into a handoff artifact. Tickets needing nobody are worked back-to-back; the session stops when the human is the blocker. Use only when the user explicitly invokes whiteboard or asks to draw, work, run, or snapshot a whiteboard/map — not for ordinary planning requests.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.