Agent Skills
› mtarcure/claude-vibe-squad
› lane-budget-estimation
lane-budget-estimation
GitHub用于估算单次调度任务规模，确保其在时间墙和提示词限制内完成。通过预检数据验证大小，拆分超限工作并明确排除范围，防止任务超时或失败。
Trigger Scenarios
需要规划单次调度任务的输入输出规模
预估任务是否能在限定时间内完成
检查提示词长度是否超出限制
Install
npx skills add mtarcure/claude-vibe-squad --skill lane-budget-estimation -g -y
SKILL.md
Frontmatter
{
"name": "lane-budget-estimation",
"audience": "chrono",
"description": "Use when sizing a single dispatch so it finishes inside one lane wall and fits the assembled-prompt ceiling—read `assembled_prompt_bytes` against `assembled_prompt_limit` from the preflight, split work that cannot finish in one wall, and name what the lane must NOT do. `scope-estimation` sizes a corpus to read; this sizes the dispatch."
}
Lane Budget Estimation
House procedure for sizing a dispatch to the two hard budgets a lane runs under: the wall clock and the assembled-prompt ceiling. Over-scoping does not degrade gracefully — it dies at the wall with nothing to show. Verify the numbers against the live preflight, not from memory.
The prompt ceiling is on the ASSEMBLED prompt
- The limit is
TRUSTED_LAUNCH_PROMPT_LIMIT = 40960bytes (dispatch_context_builder.py), applied to the packet PLUS injected briefing and absolute paths, not the packet body alone. Bothdispatch_preflight.evaluate_packet()andbuild_context()enforce the same constant. - Do not estimate from a remembered packet size — injected context and absolute path length vary by
lane and checkout. Run
bin/send-task.sh <packet-file> --dry-runand readassembled_prompt_bytesagainstassembled_prompt_limitfrom the preflight; shorten the body if it refuses.
Scope to one wall
- The wall comes from
timeout_budget_for_mode(): a flat 2700s forproject, 3600s forbounty. It is a backstop, not a per-packet dial you raise. - A deliverable that cannot finish in one wall is two packets, not one. Sequence them; the second reads the first's committed output (an uncommitted edit is invisible to the next dispatch).
- A lane that must read a large corpus AND produce a large artifact is two packets — the read burns the wall the artifact needs.
Name what the lane must NOT do
- Unbounded exploration is how a wall gets hit with nothing landed. Put explicit out-of-scope bounds in the packet: which trees not to read, which analyses to skip, when to stop and write the partial.
- Tell the lane to land what is complete and write the artifact before the wall rather than chase completeness past it — a truthful partial beats a kill with no envelope.
Size the read, then the write
- Estimate the read set first (
scope-estimationsizes the corpus), because a read that cannot fit the wall guarantees the write never starts. - Round-trips, not tool calls, are the cost unit that eats a wall: prefer whole-file reads and tool-level exclusion globs over paging, and say so in the packet if the lane tends to page.
Version History
- d5262e2 Current 2026-09-11 11:48
