t1k:estimate
| Field | Value |
|---|---|
| Module | t1k-delegation |
| Version | 2.12.24 |
| Effort | low |
| Tools | — |
Keywords: duration, estimate, eta, finish time, forecast, how long, plan eta
How to invoke
Section titled “How to invoke”/t1k:estimate<plan-dir>t1k-estimate - plan-level ETA
Section titled “t1k-estimate - plan-level ETA”Gives a plan an ETA from recorded spawn history: the model decides what each phase maps to, the CLI does every number. Runs inline in the main session (the planner); only the per-unit lookups are fanned out, to t1k-estimator.
When it runs (speed budget, D14)
Section titled “When it runs (speed budget, D14)”The CLI is called automatically: at plan finalization (plan-eta <plan-dir> --auto --record, the planner), at cook start and at team-cook start (--auto, print only), and by hand on request. It is never on the development critical path. The t1k-estimator hop is optional and explicit. features.spawnEta: false is the kill switch (plan-eta prints disabled; --auto prints nothing); planEta.autoShow: false silences only the automatic call.
The pure CLI path is the default. bun .claude/scripts/t1k-spawn-eta.cjs plan-eta <plan-dir> (no project copy → bun ~/.claude/scripts/t1k-spawn-eta.cjs) maps every phase itself from the plan’s stated agent, model and brief text, costs zero tokens and needs no agent hop. The t1k-estimator hop (step 2) is OPTIONAL and runs only on an explicit user request. There is no enforced per-hop timeout (the Agent tool has no timeout parameter): a unit that has not returned by the time the CLI result is ready is treated as unknown, and the plan-level figure is reported without it.
- Read the plan (
plans/<dir>/plan.mdand its phase files). For each phase note the stated agent, model andLane:label. If every phase states agent and model and the brief text is in the phase file, skip step 2 for it: the CLI can map it itself, zero tokens. - Fan out ONE
t1k-estimatorunit per phase (or lane) in ONE message. Read-only, so one tree is safe. Cap 8 per message at depth 0 (forkDepth.fanOutCaps); a plan with more phases goes in a second wave. Each brief names the phase file, unit id, the stated agent and model if any, and the delivery channel (final message). Estimators are cheap-tier and routable; the brief needs no transcript. - Handle each return. A well-formed
## Estimateline is used as is. A failed, empty, malformed or not-yet-returned hop makes that unitunknown; re-spawn it ONCE natively, and if it still fails leave itunknown. Never fill in a number by hand. - Run the combiner:
bun .claude/scripts/t1k-spawn-eta.cjs plan-eta <plan-dir>(no project copy →bun ~/.claude/scripts/t1k-spawn-eta.cjs). It prints ONE headlinedone by HH:MM <tz> [schedule; method; gates; delivery] n=<n> basis=<basis> validated=<evidence>(human gates and delivery are counted inside), then thesequentialandparallelschedules compared, the critical path and the per-phase rows; orunknownnaming the thin phase. - Report the CLI output verbatim with its
n,basis,validated=(orunvalidated) and anythin/unknownlabel. Never add a figure the CLI did not print, never drop thevalidated=tail, never turn an unknown into 0. Flags:--schedule sequential|parallel,--max-parallel <n>,--record,--auto,--no-gh.
What stays out of this skill
Section titled “What stays out of this skill”No quantile, percentile, critical-path or finish-time code lives here or in the agent. The single source is .claude/hooks/lib/spawn-eta.cjs (per-unit estimate()) and .claude/hooks/lib/spawn-eta-plan.cjs (the combiner), reached through t1k-spawn-eta.cjs. Design: the CLI emits facts, the model decides which phase maps to which key.