feat(kvb-release): release brief method with article and post channels
kvb-release listens once, writes one brief since the previous tag and hands each channel its slice; kvb-release-article writes the long form and kvb-release-post the short posts, each listening before it brainstorms. A project's own release skill sets file names, title and post structure, and an empty channel list means every channel the project covers. kvb-release-changelog moves its lint steps into lint.md. 🎯 Fix: 92 % 💥 Break: 3 % 💸 Cost: 279 % ⏱️ Time: 100 % 🛡️ Security: 100 % 🏆 Score: 32 🚦 Gate: ⚠️ cost 279 % > 100: operator approved the commit Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
57ab29eb0d
commit
df3cb4e4d6
8 files changed
+238
-12
No files matched your search
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: kvb-release-post
|
||||
description: >
|
||||
Write a release's short posts from its brief: LinkedIn, Mastodon, WhatsApp,
|
||||
Instagram.
|
||||
---
|
||||
|
||||
A post earns one click: one hook, one link. Input: `brief.yml`
|
||||
and `listen.yml` from the `kvb-release` skill, the channel, and the project's
|
||||
channel facts (voice, hashtags, links, length bounds) when a project skill
|
||||
passes them. No project facts live here.
|
||||
|
||||
## 1. Listen
|
||||
|
||||
Run the `kvb-think-listen` skill only for what `listen.yml` leaves open for
|
||||
this channel, such as the language of a personal message or a mention.
|
||||
|
||||
## 2. Brainstorm
|
||||
|
||||
Run the `kvb-think-brainstorm` skill on hooks for this channel and audience:
|
||||
at least three first lines; keep the strongest.
|
||||
|
||||
## 3. Write, per language
|
||||
|
||||
A project skill's structure (several benefit lines, an "Also new" line)
|
||||
replaces this one:
|
||||
|
||||
1. Hook: the first line carries the headline benefit and works on its own
|
||||
before "see more".
|
||||
2. One benefit with its proof from the brief.
|
||||
3. The brief's link, then the channel's hashtags or mentions.
|
||||
|
||||
## 4. Bounds without project facts
|
||||
|
||||
| Channel | Limit | Shown before "more" |
|
||||
| --- | --- | --- |
|
||||
| LinkedIn post | 3000 characters | about 210 characters |
|
||||
| Mastodon | 500 characters, a link counts 23 | everything |
|
||||
| WhatsApp | aim under 700 characters | the first line |
|
||||
| Instagram caption | 2200 characters, at most 30 hashtags | about 125 characters |
|
||||
|
||||
## 5. Rules
|
||||
|
||||
- Every number, name and date comes from `brief.yml`.
|
||||
- No em dashes, no placeholder, no claim the brief does not prove.
|
||||
- Write into `/tmp/release-<version>/` under the file name the project skill
|
||||
sets, else `<channel>/<language>.txt`, and report each file's character
|
||||
count against its limit.
|
||||
Reference in new issue
Block a user