li-plan

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