Weekly Portfolio Review — 2026

Owner: Rufus · Parent: Project-Management Infrastructure · Source: Rufus's dictation, 26 Oct

Summary

The question this answers each week: have I got all my projects, and if not, why not? Then, of those, which matter this week?

Planning from every task is overwhelming and planning from the mission is too vague; the useful height for a week is the project (see the tree guide draft). Projects live in many repositories, so a sweep gathers them into one table. Today that table misses many projects, and changing anything means rewriting Markdown and reloading a page.

The steps, from the dictation:

 sweep ──▷ preview ──▷ talk ──▷ see change
                                    │
                                 save ▼

1. Sweep: collect project records and their latest notes from each repository.
2. Preview: one table, one row per project, with initiative as its own column even when it repeats, then phase and owner.
3. Talk: give feedback on priorities by talking to an AI.
4. See the change quickly.
5. Save what was decided.

Prioritisation happens mostly centrally, so the week's priorities are kept centrally; everything else about a project stays in its own record, where the project lives.

What it may produce

• Data: project records in their own repositories (exists), plus somewhere central for the week's priorities (open question 2).
• Skills: the sweep and the planning skill, extended for this review.
• Tooling, maybe: a previewer that refreshes while we talk, or a small board to move projects around. Not needed yet.

Proposed order, to confirm: make the table complete first, then keep priorities, then a live view.

Issue tree

Question: How do we see every project once a week, choose this week's priorities quickly, and keep them?

1. Does the table show all our projects?
   • Which real projects have no record yet, and why? Candidates are in the project candidates note.
   • Should the table list projects with initiative as a column, rather than nesting projects under initiative headings? Rufus wants initiative as its own column.
2. Where do the week's priorities live? The data model and how we plan say project priority is set week to week in the team plan (weeks/). Options: that weekly plan, or one central priorities file the sweep merges into the table. If the second, both documents change.
3. How do we change priorities quickly in a meeting? Talking to the AI first; a previewer or board later, if needed.
4. How do we drill down from a chosen project to its tasks? Through each record's tracker link.

Related

• How we plan and track work, the planning rhythm (§3).
• Tree guide: skeleton and draft.
• Sweep script and its output, Projects by initiative.