weekly-planlisted

# Weekly Plan A calendar left alone fills with other people's priorities. Not through anyone's fault: reactive work has deadlines attached and proactive work does not, so it wins every collision, every week, forever. The failure this exists to prevent: **the full week where nothing moved.** Forty hours, thirty meetings, every one of them legitimate, and not one account in a different position on Friday than it was on Monday. --- ## What this needs **Shared context.** If an `account-context` document exists, read it first, though this skill leans on it less than most. Where it is absent, carry on. **Minimum: your calendar and a sense of what is urgent.** Enough to produce outcomes, a protected block and a decline list. **Better with** the output of `book-triage`, which answers which accounts deserve the time. Without it, this skill arranges hours around whatever is loudest, which is the problem it exists to solve. **Best with** an honest record of where last week actually went, because almost nobody's estimate of that survives contact with the evidence. --- ## Step 0: Decide the accounts before the hours **Run `book-triage` first.** Which accounts and how the hours are arranged are different questions, and doing them in the wrong order produces a beautifully organised week spent on the wrong accounts. If triage has been done, bring its list here. If not, do it, even roughly. Ten minutes of triage changes more than an hour of scheduling. --- ## Step 1: Write what