novox/hq
8
0
Fork 0
Code Issues Pull Requests 5 Releases Wiki Activity

Give the lead's ten-minute report a full and a short layout, in playbook 07

Browse Source
This commit is contained in:
jschoubben
2026-10-15 19:52:31 +02:00
parent 464833d0ef
commit 458f248c05
1 changed files with 30 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
00-META/process/07-feature-branches.md
+30 -4
View File
@@ -148,10 +148,36 @@ on, with when it started and its bound.
| a merge after ready | 5 minutes after the checks pass | read `mesh-delivery.show` for the delivery |
| a delivery plan | its class's budget (`mesh-delivery.times`), at most 30 minutes | read `mesh-controller.plans`, then `mesh-delivery.stalled` |
**Every ten minutes, and at once when something lands, stops or needs the operator,** the lead reports in a
short table: the phase and its time used against its bound, each issue with its state, every wait past its
bound and what is being done about it, and the allowance used (`anthropic-licence-manager.usage`: the week's
and the session's). Times are local and absolute.
**Every ten minutes, and at once when something lands, stops or needs the operator,** the lead reports, in
one of the two layouts below. Times are local and absolute; every number has its unit and its bound or
baseline; an issue is named by its number and a few words, never by its number alone.
**The full layout** (in the session):
```
Feature <slug> · step <n> of <m> · phase <name>, <minutes used> of <bound> min
Issues: <landed> of <total> landed · <fixing> fixing · <waiting> waiting
| Issue | What | Repository | State | Since | Bound |
|---|---|---|---|---|---|
| 652 | assignments on the bus | mesh-controller | landed | 14:02 | |
| 736 | placement words leave the layers | mesh-controller | fixing, 23 min | 13:51 | 30 min |
| 751 | config keys named | mesh-catalog | waits for 736 | 13:40 | |
Past its bound: <the wait, how long, what is being done> — or "none"
Needs you: <one line per question, with my recommendation> — or "nothing"
Allowance: week <n> % (<+d> since the last report), session <n> %
Next: <the next action, one line>
```
**The short layout** (on a channel such as Telegram, or when nothing changed but time):
```
<slug> step <n>/<m> · <phase> <used>/<bound> min · <landed>/<total> landed · past bound: <none | what> · needs you: <nothing | what> · week <n> %
```
A report says what changed since the last one first; an unchanged table is not repeated, the short layout
says it instead.
## The context of the lead's own session