Open for commentsSelect text to comment

Pilot: weekly portfolio review MVP

TL;DR: The MVP from the brief and design is built: scripts/review_prepare.py, scripts/review_render.py and a review mode in the planning skill. A fresh Sonnet agent ran it end to end from the skill alone on real data, with scripted feedback standing in for Rufus at both gates, and passed all ten checks. The trial output is a test record only; the gate decisions in it were scripted, not Rufus's.

Run 1: Sonnet, 26 Oct

Files: trial page, trial JSON, trial week plan.

#CheckResult
1Files exist, renderer exits 0Pass
2Complete tablePass: 30 projects = 30 open in the cache (27 active, 3 iced)
3Gaps with fixesPass: 56 gaps, all with a fix. ais-61b/ais-q7s are now linked to 2622, so the epic-no-project example is ais-qdf instead
4Shortlist with reasons and questionsPass: 7 projects, 4 questions
5Gate 1 appliedPass: course first, comms and Wisdom to not-this-week, Film and Retreat iced, feedback logged, page re-rendered
6Drill-down with real bead IDsPass: every key task checked with bd show
7Gate 2 appliedPass: one key task for 2620, feedback logged
8Harvest splitPass: 7 permanent edits, 4 Beads changes, goal, focus, people; nothing applied
9No side effectsPass: the only changes in sibling repos were other sessions' commits (comms, research); no weeks/2026-10-26.md
10From the skill alonePass: no clarifying questions before gate 1

What it found that was useful: the Collective Action course's key tasks are unassigned two days before it starts; the SoR launch epic has no ready task; the Global Connection Call's setup tasks (Zoom, Luma) were due in early October and are still open; three records share one epic (2602, 2610, 2613).

Fixes after the run

  • The readiness rule marked running work as "needs planning" just because the record had no issue tree. Now a missing tree on running work is "ready, planning thin", and unassigned or overdue key tasks are flagged.
  • Gaps were 64 at first. Owner gaps now count top-level epics only, and the page groups gaps by kind with the most consequential first (repos without a record, then epics without a project).

Not yet tested

  • An Opus run (Sonnet passed; Opus is expected to do at least as well).
  • A second week, where last week's review supplies the priority history and ice decisions.
  • Applying a harvest for real (record edits in other repos, Beads changes).
Built with LogoFlowershow