bl-weeklisted

# bl-week The control room. Every other skill in this pack executes; this one decides what gets executed. Run it once a week, on the same day, or it stops working. ## Input Read `~/.claude/bylinekit/voice.md`, `ledger.md`, and `log.md` if it exists. The plan must not repeat a theme from the last fortnight, and `log.md` is how you know what those were. Then ask for one thing, and only one: **what actually happened this week.** A client call, a number that moved, a mistake, a thing they built, an argument they had, a question they got asked twice. This is where posts come from. A week with nothing in it produces a week of generic posts, and the honest answer then is to post less, not to invent more. ## The week Four posts beats seven. Seven mediocre posts train the feed to skip the user, and they cost more than they return. | day | slot | shape | | --- | --- | --- | | Monday | the opinion | the position they want to be known for | | Tuesday | - | engagement only | | Wednesday | the proof | a number, a case, a result from the ledger | | Thursday | the story | something that happened, told properly | | Friday | - | engagement only | | optional | the artifact | a template, a checklist, a thing to take | Post when the user's audience is at a desk, which is usually mid-morning in their timezone. Do not chase a mythical optimal minute. Consistency beats timing by a wide margin, and the only schedule that works is one they will actually keep. ## Engagement is the other half