build-epic
Build an epic from its tech lead prompt to release QA, through the user's repo sessions (one per repo in the team's roost config). If the stories have no kickoff comments yet, it first sends the epic's tech lead prompt to the lead repo's session, brings the plan to the user for approval, and has the kickoffs posted. Then it runs run-slice for each story in order, slice-handoff between stories, the epic's "before release" work, review-epic, close-out-epic and release-qa. Starts without asking and keeps going on its own; stops only for decisions that are the user's (the plan, each slice's checkpoints, each handoff's sorting table) and for real blockers. Answers "where are we on the epic?" from the tracker, GitHub and its state file. Use when the user says "build PROJ-X", "build the epic", "develop PROJ-X", "start building PROJ-X", "do all the slices", "take this epic to release", or the older "run the epic" and "run the rest of PROJ-X". Run it from a separate orchestrator session, not fr
Beakpoint-Insights · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Beakpoint-Insights/roost --skill build-epic技能说明
name: build-epic description: Build an epic from its tech lead prompt to release QA, through the user's repo sessions (one per repo in the team's roost config). If the stories have no kickoff comments yet, it first sends the epic's tech lead prompt to the lead repo's session, brings the plan to the user for approval, and has the kickoffs posted. Then it runs run-slice for each story in order, slice-handoff between stories, the epic's "before release" work, review-epic, close-out-epic and release-qa. Starts without asking and keeps going on its own; stops only for decisions that are the user's (the plan, each slice's checkpoints, each handoff's sorting table) and for real blockers. Answers "where are we on the epic?" from the tracker, GitHub and its state file. Use when the user says "build PROJ-X", "build the epic", "develop PROJ-X", "start building PROJ-X", "do all the slices", "take this epic to release", or the older "run the epic" and "run the rest of PROJ-X". Run it from a separate orchestrator session, not from inside any of the repos.
Build Epic
You coordinate a whole epic the way run-slice coordinates one story. You never edit, build or run tests in any repo yourself. One session per repo in the config's repos does the work, through SendMessage, exactly as run-slice describes. The lead session is the session of planning.lead_repo.
First, load the team config with roost-config.
Being asked to build the epic is the go-ahead. Don't ask for another one, at the start or between slices. Tell the user what you started and why, and keep going.
Inputs
- EPIC: the epic's ticket key.
- A session for each repo the epic touches must be open. If one isn't, that's a blocker: ask the user to open it, and stop.
Status: "where are we on the epic?"
Use run-slice's Status for an epic: one row per story in story order, then the step table for the story in progress. Add one line under it: the counts from the epic's Carry-over comment ("before release: 2, later: 5"). Read-only; send nothing.
1. Find where the epic is
Before anything else, new build or resumed: work out which roost you run ("Which roost is running" in roost-config), then do run-slice's step 0: find the sessions and check every one runs the same roost as you, stopping if they don't. Record all of them in EPIC.md and say yours in your first report. Planning (step 2) and the before-release work (step 4) send work without going through run-slice, so this check can't wait for it.
- Story order: the order the epic's build guide or its stories give ("Slice 1", "Slice 2", …); if neither says, the order the stories were created in.
- Each story's state: at
tracker.statuses.ready_for_releaseor later is done; otherwise userun-slice's resume check for it. - Your record: read
<team.state_dir>/EPIC.mdif it exists: the story order, the current story, the session names, and the IDs of the epic's Release order and Carry-over comments. Check it against the tracker and GitHub the wayrun-slicechecks its state file. - The epic's comments: Release order and Carry-over.
- Kickoffs and plan: whether every story has a kickoff comment for each repo it touches (each titled with that repo's
kickoff_title), and whether a plan already exists: the plan path and stack in your state file, or a plan commit on agh stacknamed for the epic in the lead repo.- Every story has its kickoffs: planning is done; go to step 3.
- Some stories have kickoffs and others don't: posting was interrupted. Ask the lead session to post only the missing ones from the approved plan, then do step 2's check (item 5).
- No kickoffs, but a plan exists: planning stopped before or at approval. Pick up at step 2's checkpoint with that plan; don't send the prompt again, which would start a second stack.
- No kickoffs and no plan: start at step 2.
Tell the user in one short table where the epic is and where you're starting, then start.
2. Plan the build
Only when the stories have no kickoff comments yet. The plan is written by the lead session, acting as the epic's tech lead, from the prompt shape-epic attached to the epic.
- Get the prompt: the epic's attachment
<EPIC> Tech Lead Prompt.md(see "Read an attachment" in the tracker adapter). If there isn't one, that's a blocker: tell the user to runshape-epic's handoff phase, and stop. - Send it to the lead session word for word, with the first line "build-epic: plan EPIC as its tech lead". The prompt itself says to stop for approval after the plan, and what to report. As soon as the reply names the plan's path and stack, record them in the state file, so a restart resumes at the checkpoint instead of planning again.
- Checkpoint: the plan. When the lead session replies, show the user its plan in one message: the plan's path and stack, each story's tasks for each repo in order, the current-state findings, the blockers, the open questions, any contradictions it found, and its Rollout needed line. Every current-state finding and every contradiction must cite its
file:line, or a query and its result; send any that doesn't back to the lead session before you show the plan, and never fill the gap from memory. Treat a claim inferred from names or dates (a migration's date as the age of the data, a code comment as the author's intent) as unchecked until it's checked against the data or the user. If the plan says no but it adds a migration, a backfill or a flag, say so and recommend yes. Recommend an answer for each open question. If the user asks for changes, send them to the lead session and show the updated plan; repeat until they approve. - Approve: tell the lead session the user approved, and to post the kickoff comments and the Release order comment (its prompt's section 5). Wait for its report.
- Check: read every story's comments yourself, not just the report. Every