weekly-planning

Weekly planning converts retro findings and backlog items into a prioritized set of measurable outcomes. It groups tasks by surface, applies an Eisenhower split, and defines commitments with clear checks before routing work. Results include assigned owners and routed issues.

Config-driven routing uses CLAUDE.md configuration to assign generated weekly outcomes to the correct repositories. It applies W{NN} labeling and integrates with project boards to ensure delegated work reaches the right codebase automatically.

Yes, the weekly planning process generates a delegation matrix with assigned owners across multiple repos. It reads calendar and issue data to produce measurable outcomes, routing each item to the correct repository using CLAUDE.md config.

The best way to plan weekly project outcomes is defining commitments with measurable checks rather than listing tasks. This approach maps your calendar, groups work by surface, applies an Eisenhower split, and creates routed issues with assigned owners.

Run weekly planning after your weekly retro, during Monday or Tuesday planning sessions, or when you need a weekly plan with outcomes and a delegation matrix. It requires reading calendars and issues to generate measurable, routed outcomes.

Yes, CLAUDE.md config is required for routing work to the correct repositories using W{NN} labeling and project boards. It drives the automated assignment of prioritized weekly outcomes to the appropriate codebases.