What problem does it solve? When a new framework version ships, every communications document — changelog, blog, skill reference cards, and guide pages — must be updated consistently, committed, and deployed. Doing this by hand is slow and error-prone, and entries often drift in style or get skipped entirely. ## Core Features & Use Cases - Coordinated doc updates: Reviews a full inventory of communications files (CHANGELOG.md, blog.html, skills-reference.html, guide pages) and updates only what is relevant to the shipped version. - Style-matched entries: Reads recent blog and changelog entries first, then writes new entries that match existing HTML structure, badge classes, and tone exactly. - One-pass execution: Commits changes to GitHub, pushes, and deploys the docs site to Cloudflare Pages via wrangler in a single run, then reports results back to the invoking curator. - Use Case: After shipping framework version v2.4.0, the curator invokes this sub-agent with a structured brief; it adds the changelog entry, publishes a blog post, updates affected skill cards, commits, pushes, and deploys without further input. ## Quick Start Invoke this sub-agent with a version brief containing the version number, date, summary, affected skills, and watch-for items so it updates all communications docs and deploys them.
