mpc_to-tickets
Break a plan, spec, or the current conversation into a set of tickets, each declaring its blocking edges, its Result and its Marketing line, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- mpc_to-tickets
- description
- Break a plan, spec, or the current conversation into a set of tickets, each declaring its blocking edges, its Result and its Marketing line, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
- disable-model-invocation
- true
03 SKILL.md 正文
To Tickets
Break a plan, spec, or conversation into a set of tickets: each one makes one result (or one complete part of a result) that can be checked on its own, and declares the tickets that block it, where its result goes, and whether it is marketing work.
The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /boarlabs:boar_setup.
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.
2. Read the context (optional)
If you have not already, read the repository's context: GLOSSARY.md, ADRs, research notes and the Q&A logs under docs/qna/. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
3. Draft the tickets
<ticket-rules>
- Each ticket makes one result, or one complete part of a result, that can be checked on its own
- Each ticket is sized to fit in a single fresh context window
- Research that several tickets need comes first, as its own ticket
</ticket-rules>
Give each ticket its blocking edges: the other tickets that must complete before it can start. A ticket with no blockers can start immediately.
Give each ticket its two required lines. There is no default for either:
- Result: the platform (a Google Doc or Drive file, a ClickUp task or doc, a Miro board, a Claude artifact, …), the place on it (a folder, list or board, with a link) and the result's name. Only a platform the session can write to through its connectors counts.
- Marketing:
yesorno, taken from the spec; a ticket differs from the spec only where the spec says so. Withyes,/boarlabs:mpc_implementuses thechs_*skills that fit; withno, it uses none.
If you cannot fill either line for a ticket, ask the user before publishing.
4. Quiz the user
Present the proposed breakdown as a numbered list. For each ticket, show:
- Title: short descriptive name
- Blocked by: which other tickets (if any) must complete first
- What it delivers: the result this ticket makes
- Result: platform, place, name
- Marketing: yes or no
Ask the user:
- Does the granularity feel right? (too coarse / too fine)
- Are the blocking edges correct: does each ticket only depend on tickets that genuinely gate it?
- Should any tickets be merged or split further?
Iterate until the user approves the breakdown.
5. Publish the tickets to the configured tracker
Publish the approved tickets. How depends on the tracker /boarlabs:boar_setup configured; the tickets are the same either way, only the shape of the blocking edges changes:
- Local files → write one file per ticket under
.scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from01in dependency order (blockers first). Each file's "Blocked by" lists the numbers/titles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file. - A real issue tracker (GitHub, Linear, …) → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking relationship where it has one; otherwise set each ticket's "Blocked by" to the blocking issues. If the source was an existing issue, make each ticket its sub-issue (tracker doc's operation). Apply the
ready-for-agenttriage label unless instructed otherwise; the tickets are agent-grabbable by construction.
Work the frontier: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.
Do NOT close or modify any parent issue.
<local-ticket-template>
<NN>: <Ticket title>
What to make: the result this ticket makes, from the reader's perspective.
Result: the platform, the place (with a link) and the name.
Marketing: yes or no.
Blocked by: the numbers/titles of the tickets that gate this one, or "None (can start immediately)".
Status: ready-for-agent
- [ ] Acceptance criterion 1
- [ ] Acceptance criterion 2
</local-ticket-template>
<issue-template>
Parent
A reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).
What to make
The result this ticket makes, from the reader's perspective.
Result
- Platform: where the result lives
- Place: the folder, list or board, with a link
- Name: the result's name
Marketing
yes or no
Acceptance criteria
- [ ] Criterion 1
- [ ] Criterion 2
Blocked by
- A reference to each blocking ticket, or "None (can start immediately)". Omit this section when blockers were set as native edges.
</issue-template>
In either form, point at the spec, the Q&A log and research notes rather than copying them.
04 同仓库更多 Skills
mpc_writing-shape
Writing, exploit: shape raw material into an article, paragraph by paragraph.
mpc_writing-fragments
Writing, explore: mine raw fragments, no structure yet.
mpc_writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
mpc_writing-beats
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
mpc_wayfinder
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.
mpc_wait-what
Stop. That last message did not land: re-pitch it.