slice-handoff
Close out a finished slice of an epic before the next one starts. Sorts everything the slice left open (follow-up tickets, deferred bugs, unautomated scenarios) into the next slice, before release, or later; keeps one Carry-over comment on the epic; runs every test in the epic so far, so a later slice can't quietly break an earlier one, and makes the tracker match; rewrites the next slice's kickoff comments so they're current; and checks every repo's stack is healthy. Use after run-slice finishes a slice (its last step runs this), or when the user says "wrap up PROJ-X", "get ready for the next slice", "what's carried over from slice 3", or "is the epic still green".
Beakpoint-Insights · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Beakpoint-Insights/roost --skill slice-handoff技能说明
name: slice-handoff description: Close out a finished slice of an epic before the next one starts. Sorts everything the slice left open (follow-up tickets, deferred bugs, unautomated scenarios) into the next slice, before release, or later; keeps one Carry-over comment on the epic; runs every test in the epic so far, so a later slice can't quietly break an earlier one, and makes the tracker match; rewrites the next slice's kickoff comments so they're current; and checks every repo's stack is healthy. Use after run-slice finishes a slice (its last step runs this), or when the user says "wrap up PROJ-X", "get ready for the next slice", "what's carried over from slice 3", or "is the epic still green".
Slice Handoff
A slice rarely ends with nothing left over. Exploratory testing finds bugs that wait, code review produces "ticket for later" items, a later slice reopens an earlier slice's test, and the plan changes under the next slice's kickoff. This skill deals with all of it once, in one place, before the next slice starts.
It changes the tracker and reads GitHub. It changes no code. The one step that runs tests goes to the session in the repo that owns them.
First, load the team config with roost-config.
Inputs
- DONE: the story that just finished.
- NEXT: the next story in the epic's story order. If DONE was the last slice, there is no NEXT: skip step 5, and anything sorted "next slice" becomes "before release".
- EPIC: DONE's parent.
1. Gather what's open
Read everything first; decide nothing yet. Don't trust that the slice recorded everything: look wider than its links, and compare the sources.
-
The slice's own record: DONE's "slice done" comment, with its Left open table, and its
run-slice checkpoint:comments. Every checkpoint row should have an outcome you can check: a commit or PR for "fix now", a ticket key for "ticket for later", a reason for "skip". Every ticket in the Left open table should exist, be open, and have EPIC as its parent. -
Open tickets, found two ways (the tracker adapter's common searches):
- linked: open tickets linked to DONE;
- wide: everything in the project created while the slice ran (from DONE's first kickoff message to its "slice done" comment) whose parent is EPIC or whose text mentions DONE.
Include anything the epic's Carry-over comment already lists as "next slice" for DONE that wasn't done.
-
Compare them. Each difference is a possible record gap:
- A ticket only the wide search finds is a candidate, not a fact: it shares the epic and the dates, but may belong to other work. Don't change it yet. It goes in step 2's table with "From this slice?" for the user to confirm, and is linked to DONE only if they do.
- A checkpoint row with no outcome, or a "ticket for later" with no ticket: put it in step 2's table; don't create the ticket until the user has seen it.
- A ticket already linked to DONE but missing its parent or Components: set them now; it's DONE's ticket either way (see "Set or clear a parent" in the tracker adapter).
A concern that only ever lived in a session's report can't be found from the tracker. Step 2 asks the user about anything run-slice's state file mentions that has no tracker record.
-
Every test in the epic: the tests linked to each story in EPIC so far, with their labels and statuses, leaving out retired tests (the tests adapter's "Retire a test").
-
The stacks: every PR for EPIC in each repo, its head, its base, and each check's newest completed result (
gh pr view <n> -R <repo.github> --json statusCheckRollup; ignore runs a newer push cancelled). -
Plan changes: commits on the plan branch since the slice started, and the decisions recorded in
<team.state_dir>/DONE.mdif it exists. -
NEXT's kickoff comments, one per repo, titled with each repo's
kickoff_title.
Leave the tests' shared setup out of the open tickets (the tests adapter's "Shared setup", where it's a ticket: it's part of the epic's tests), and close any whose tests are all done. Leave manual tests with When: after release out too ("Manual tests" in the tests adapter): they wait for the release, like person-owned tasks; name them in the report. Leave person-owned tasks (labelled tracker.person_task_label) out of all of this: they aren't carried-over work. If one's "When" is "after" DONE, put a reminder for its owner in the report's 🙋 Your turn block.
2. Sort the carried-over work
Put each open item in exactly one place, judging it the triage-ticket way (is it real, who does it hurt, how badly):
| Place | When |
|---|---|
| Next slice | NEXT changes the same code or screen, or NEXT can't be right without it. It's cheapest to fix while that code is open again. |
| Before release | It must be fixed before the epic ships (security, data loss, a 5xx from a public endpoint, a broken main flow) and NEXT doesn't touch it. |
| Later | Everything else. It keeps the epic as its parent but doesn't hold up the release. |
Show the user one table, with a recommendation and a one-line reason for each item:
| # | Item | From | Recommendation | Why |
|---|---|---|---|---|
| 1 | PROJ-2819 Get started names the wrong key | 2789 exploratory | Next slice | 2790 changes the key list Get started reads |
| 2 | PROJ-2830 Billing page spacing | From this slice? (found by the wide search) | Later, if from this slice; otherwise leave it alone | Created during the slice under the epic, but not linked to it |
This is the only stop in the skill. Wait for the user's decisions, then carry them out without asking again. A candidate the user confirms as this slice's gets its "relates to" link to DONE, and its parent and Components if missing; one they don't confirm is left untouched.
3. Keep the epic's Carry-over comment
EPIC has one Carry-over comment (create it the first time), next to its Release order comment. It lists every carried item still o
阅读完整来源 ↗