菜单
Creates and maintains docs/tickets/plans/PLAN-NNN plans that cluster related collisionspike tickets. Use for multi-ticket operator plans, plan lifecycle updates, bidirectional plan/ticket links, and closing plans when all member tickets are done.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/collisionengineers/collisionspike --skill ticket-plan命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Current Box REST API reference for collisionspike archive integration, including server-side CCG authentication, folders, file requests, shared links, webhook signatures, retry behavior, and least-privilege scopes. Use when building or validating services/functions/box-webhook or an archive caller.
EVA Sentry API v1.2 reference for collisionspike, covering authentication, the eight endpoint families, the canonical twelve-field payload, image ordering, idempotency, and server-side submission. Use when changing EVA contracts, services/functions/eva-sentry, or any submission caller.
Distills operator drop-notes and sample emails/documents into new collisionspike tickets under the status-folder system (docs/tickets/backlog|blocked|next|now|verify|done/TKT-NNN folders with frontmatter, evidence/, changes.md, verification.md) and adds them to BOARD.md. Use when creating a ticket from raw operator material, a new work-todo-spike stub, or a small new work item.
基于 SOC 职业分类
正在显示 SKILL.md
| name | ticket-plan |
| description | Creates and maintains docs/tickets/plans/PLAN-NNN plans that cluster related collisionspike tickets. Use for multi-ticket operator plans, plan lifecycle updates, bidirectional plan/ticket links, and closing plans when all member tickets are done. |
| disable-model-invocation | true |
Workflow for creating or maintaining a ticket plan under docs/tickets/plans/. A plan clusters related
TKT tickets but never moves with ticket status changes.
- [ ] Confirm the material is multi-ticket, not one atomic ticket
- [ ] Allocate PLAN-NNN by scanning docs/tickets/plans/PLAN-*.md
- [ ] Create/update PLAN-NNN-<slug>.md from templates.md
- [ ] Ensure every listed TKT exists (or create tickets with ticket-distill)
- [ ] Add plan: PLAN-NNN to every member ticket
- [ ] Ensure the plan's tickets list includes every member ticket that points back
- [ ] Link the plan from docs/tickets/README.md / BOARD.md as needed
- [ ] node scripts/checks/check-tickets.mjs && node scripts/checks/check-doc-links.mjs
Use a plan when the operator gives a programme of work that naturally decomposes into several tickets, or when multiple existing tickets share an execution sequence/dependency graph. Do not use a plan for one atomic bug; create a normal ticket instead.
Plans live at docs/tickets/plans/PLAN-NNN-<slug>.md and begin with:
---
id: PLAN-NNN
title: Short programme title
status: active # active | done | superseded
tickets: [TKT-001, TKT-002]
depends-on: [PLAN-001] # optional
---
Body guidance:
Scan all existing docs/tickets/plans/PLAN-*.md; allocate max(NNN)+1. Never reuse an id.
tickets: entry must resolve to an existing ticket.plan: PLAN-NNN frontmatter.plan: PLAN-NNN, the plan should list it in tickets:. check-tickets warns when this drifts.| Status | Meaning |
|---|---|
active | Some member tickets are open, queued, verifying, or blocked |
done | All member tickets are done and the plan close-out notes are recorded |
superseded | Replaced by another plan or decision; link the successor |
Close a plan only after all member tickets are done or explicitly transferred/superseded.
node scripts/checks/check-tickets.mjs
node scripts/checks/check-doc-links.mjs