Problem
When Chief is running through a PRD with many user stories, there's no visibility into how long the remaining work will take. Users have to manually cross-reference progress.md, claude.log, and git history to figure out where things stand and when the agent will finish.
Proposed solution
Display an ETA / estimated time remaining in the dashboard based on observed velocity.
Chief already has the data needed to calculate this:
1.
2. Total stories — parsed from the PRD 3. Completed stories — tracked in progress.md
3. Per-story duration — derived from commit timestamps or iteration start/end times in claude.log
Suggested formula
avg_minutes_per_story = total_elapsed_minutes / completed_stories
eta_minutes = remaining_stories × avg_minutes_per_story
A weighted moving average (giving more weight to recent stories) would be even better, since early stories often take longer due to codebase exploration and patternestablishment.
Where to show it
- TUI dashboard — next to the progress bar or story list, e.g.
Progress: 11/18 (61%) · ~60 min remaining
- Terminal title (optional) — so users can see progress without switching windows
Edge cases to consider
- Stories with very different complexity (could show a range instead of a point estimate)
- Overnight gaps between sessions (exclude idle time from velocity calculation)
- First 1-2 stories may not be representative (show "Calculating..." until ≥3 stories are done)
Why this is useful
I just had an 18-story PRD running and had to manually analyze git timestamps and progress.md to estimate completion — something Chief could trivially automate with data it already collects.
Problem
When Chief is running through a PRD with many user stories, there's no visibility into how long the remaining work will take. Users have to manually cross-reference
progress.md,claude.log, and git history to figure out where things stand and when the agent will finish.Proposed solution
Display an ETA / estimated time remaining in the dashboard based on observed velocity.
Chief already has the data needed to calculate this:
1.
2. Total stories — parsed from the PRD 3. Completed stories — tracked in
progress.md3. Per-story duration — derived from commit timestamps or iteration start/end times in
claude.logSuggested formula
avg_minutes_per_story = total_elapsed_minutes / completed_stories
eta_minutes = remaining_stories × avg_minutes_per_story
A weighted moving average (giving more weight to recent stories) would be even better, since early stories often take longer due to codebase exploration and patternestablishment.
Where to show it
Progress: 11/18 (61%) · ~60 min remainingEdge cases to consider
Why this is useful
I just had an 18-story PRD running and had to manually analyze git timestamps and progress.md to estimate completion — something Chief could trivially automate with data it already collects.