weekly-planning

# Weekly Planning ## Overview Turn retro findings + existing backlog into a prioritized week with clear outcomes, issues in correct repos, and delegation matrix (founder vs agent). ## When to Use - After weekly retro is complete - Monday/Tuesday when planning the week - When user says "план на неделю", "приоритизация", "что делаем" ## Iron Rule: Planning Is Not Execution Weekly planning creates a plan. It does not execute the plan. Allowed during planning: - Gather context needed to choose outcomes - Read calendars, issues, project boards, CRM/backlog files, and recent notes - Draft outcomes, issue proposals, and board updates Not allowed during planning: - Start implementation work for a chosen outcome - Create deliverables, briefs, proposals, content, code, or production changes - Spawn executor agents for work that belongs to the coming week If the user asks to "do this now" while planning, finish or pause planning first, then handle that as a separate execution task. ## Process ```dot digraph planning { rankdir=TB; node [shape=box]; collect [label="1. Collect all tasks"]; calendar [label="2. Map calendar"]; group [label="3. Group by surface"]; eisenhower [label="4. Eisenhower split"]; outcomes [label="5. Choose outcomes"]; issues [label="6. Create issues\nin correct repos"]; board [label="7. Add to board\nwith W{NN} label"]; collect -> calendar -> group -> eisenhower -> outcomes -> issues -> board; } ``` ### 1. Collect all tasks Sources ...