Team planning pilot — 5 October 2026

Status: first trial of the team planning skill and scripts/team_sweep.py. Tracked in lip-tqk.9. The draft week below is a proposal, not an agreed plan; nothing in Beads or GitHub was changed.

Decisions taken into the design (Rufus, 5 October)

Read live across repos; no cache. A full refreshed team sweep took 46s; without --refresh, about 12s.
GTD-style "what's next" (in progress + bd ready by priority), not a due date on every bead. Due dates only where genuinely fixed.
Repos come from active initiatives' and projects' github:/tracker: fields, checked out as siblings of this repo.
Week first (team and per person); month later.
plan-for-delegation sweep becomes the prep step; its spec mode stays in the global skill.

Draft week

The draft team plan is in weeks/2026-10-05.md.

Fix in trackers (found by the sweep)

Overdue, probably done: calls-hwt.1, .14, .15, .17 (rufus, due 30 Sep–1 Oct) are still open. Close or re-date.
No owner: calls-hwt.8, .9; active projects 2601, 2602, 2604, 2607, 2608, 2609, 2610, 2612.
Legacy assignees: 12 asdra@lifeitself.org, 6 rufus@lifeitself.org; claimed items show Rufus Pollock because bd update --claim writes the git user name. The sweep matches all three, but slugs are the convention.
Fae has assigned work (lip-87i) but no people/ record.
Design repo holds the brand work but no record links it (sweep needs --extra-repo design). Candidate: add github: to the rebrand/rollout projects or the Seeds of Renaissance initiative.
Not readable: next.lifeitself.org and research Beads need a schema migration (any bd write migrates it); secondrenaissance (Seeds of Renaissance initiative) is not checked out; Asana trackers (social media, podcast) and GitHub Projects boards (courses, publications) are not read.
Noise: community GitHub has 80 open issues, most historical; it dominates the incubator's ready list.

What worked / what didn't

Worked: one live read gives a usable team picture and per-person lists (assigned + unassigned ready work in repos they own). sor-community already uses slugs and real due dates; it is the model.
Didn't: a git fetch hung once on SSH, so fetches now time out at 60s with no prompts. Person views include the whole planning-repo pool for anyone owning a planning-tracked record, which is long for Rufus.