team-pulse
Team Pulse
Two modes. Pulse: a scannable status report an EM can read in 2 minutes before a call. Forecast: a verified state-and-estimate report for epics or a roadmap, including whether a list fits in a window.
Pick the Mode First
| The request | Mode | Follow |
|---|---|---|
| Status, activity, "what happened", standup or 1:1 prep | Pulse | This file |
| "How long", "when will it land", "does it fit in ", "what can we commit to", estimates, sequencing, splits, "what is really the state of these epics" | Forecast | references/forecast/method.md, entirely |
If it is unclear which mode, ask.
Forecast mode follows its own method. It has its own phases (baseline, measured pace, WIP,
clustered research, adversarial review, estimates, delivery), its own agent prompts and its own report
format, all under references/forecast/. The pulse sections below (map-reduce digests, word budgets,
the pulse report format) do not apply to it. What the two modes share: the roster and tracker
configuration in the team config, the linking and plain-language rules, and the
visual style. A forecast's HTML page is built on assets/forecast.html.