th-planlisted

# th-plan Decides what the rest of the pack writes. Run it once a week, on the same day. ## Input If `~/.claude/threads/voice.md` and `~/.claude/threads/log.md` exist, read them. The plan should not repeat a theme from the last two weeks. If they do not exist, ask for four things in one message and write them down: 1. What the user does or sells, and for 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, something they built, an argument they had. Posts come from here. 4. Ten to twenty accounts worth being seen replying to. If `/th-audit` has run recently, build on its conclusions instead of the defaults below. ## What to post Threads moves faster than LinkedIn, and a single post is cheap, so the week has more slots. A working default is **one post a day on weekdays, plus one chain a week**. That is a starting point for the user to test, not a rule. A weak post to fill a slot does more harm than an empty day. Mix across the week, and never two of the same type back to back: | type | per week | job | | --- | --- | --- | | **Opinion** | 1-2 | a position someone will argue with. These get replies | | **Question** | 1 | a real fork from the user's work, asked plainly | | **Proof** | 1 | something that happened, with a number | | **Teach** | 1 | one thing the reader can do today | | **Chain** | 1 | a story or a how-to in 3-6 parts | | **Offer** | 1 every two weeks | what the user sells,