li-planlisted

# li-plan The control room. Everything else in this pack executes; this decides what gets executed. Run it once a week, on the same day. ## Input If `~/.claude/linkedin/voice.md` and `log.md` exist, read them - the plan should not repeat a theme from the last fortnight. If they do not exist, ask for four things and write them down: 1. What the user sells, and to whom. 2. The three or four themes they want to be known for. 3. What actually happened this week - a client call, a number, a mistake, a thing they built, an argument they had. This is where posts come from. 4. Ten to twenty people or companies worth being visible to. ## What to post Four posts a week beats seven. Consistency is a floor, not a target, and the fifth post of a week is almost always the weak one that drags the average. Mix across the week, never two of the same type back to back: | type | share | job | | --- | --- | --- | | **Proof** | 1 per week | something that happened, with a number | | **Opinion** | 1 per week | a position that could lose you followers | | **Teach** | 1 per week | one thing the reader can do today | | **Story** | 1 per fortnight | a scene with dialogue and a cost | | **Offer** | 1 per fortnight | what you sell, said plainly, no apology | For each slot give: the theme, the specific angle drawn from what actually happened this week, and the hook formula number from `li-post/hooks.json` that fits it. Not a topic - an angle. "AI" is not a plan. "The proposal we lost because