pb-newsletter
Turn a pb-ship recap, a changelog range or a quick recap into a newsletter email draft where every claim cites a source line, and send it only after GO. Use for "newsletter from the recap", "write the
SKILL.mdskills/playbooks/pb-newsletter/SKILL.md
GitHubNewsletter from a recap
What you get: a newsletter draft (subject, preheader, body) built only from facts you can trace, sent after your GO.
Inputs
- recap — a pb-ship run log, a CHANGELOG range, or quick-recap output
- audience — who reads it, asked once
- A save folder — asked once; default
./pb-newsletter-<date>/
Steps
- Check the store —
test -d ~/.claude/skills/brand-voiceandtest -d ~/.claude/skills/email-ops→run-log.md(create the folder only after the recap file or range is confirmed readable) — an absent item is logged "Missing store item: <name>, install via aos-store" and the run continues with copywriting - quick-recap — the recap →
facts.md, one line per fact with its source line or file — every fact cites a source - brand-voice if present, else copywriting —
facts.mdand the audience →newsletter.mdwith subject, preheader and body, no claim outsidefacts.md— stops for approval, edits applied until approved - [GO] send newsletter — through a connector the human names (email-ops if present); the recipients or list, the subject and the full text shown first. The run stops here until the human types GO. Without a connector, the GO releases a hand-off file instead:
newsletter.mdwith the recipient list, you send it yourself. A sending connector is not hook-guarded, so this GO is its only guard. The GO covers exactly the audience and message shown; a changed audience needs a fresh GO.
Run log: run-log.md in the save folder, never committed
Rules
- Anything other than the literal GO (case-insensitive) is not a GO; a GO covers only that one step, one time.
- A failed check stops the run: write the failure into the run log and report. No silent retries.
- Write one run-log line per step as it completes (
N. done|skipped|failed — artifact — check result) andWAITING FOR GO: <step>at each gate.