weekly-plan

The hourly auto-pylot is a tight executor: it triages cheaply and dispatches the top 1–3 issues. It can't afford a deep roadmap dive every hour, and it has no human to ask. weekly-plan is the interactive counterpart you run with a person in the loop — in a Claude Code session or a pylot chat session — to set direction for the week. It shapes the backlog and the goals; the hourly executes them.

This is not a cron. It asks the owner questions and waits for answers, so it only runs where a human can respond. There is no push channel — every question and the final digest are presented in-session.

One team per session. Run it once per team, sequentially. Each session reads and mutates ONLY its own team — no other team's metrics, costs, or config appear anywhere in the session.

Division of labor: weekly-plan shapes (score, rank, ask, reconcile, triage, decompose, write goals, set budget, activate the hourly). The hourly executes (dispatch). One clean kill beats five grazing shots.

When to Use

• The owner opens a CC or pylot-chat session to plan a team's week before turning the hourly loose.
• The backlog feels stale, mislabeled, or unfocused and the goals need a reset.
• After a big merge wave, to re-aim the hourly.

Invocation

/weekly-plan team [org/repo]      # e.g. /weekly-plan infra — repo arg optionally narrows to one of the team's repos