# Ce Promote

Draft launch or promotion copy for a shipped feature.

- Repository: https://github.com/EveryInc/compound-engineering-plugin (25818 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add EveryInc/compound-engineering-plugin --skill ce-promote -g -a claude-code -y`
Codex: `npx skills add EveryInc/compound-engineering-plugin --skill ce-promote -g -a codex -y`
Cursor: `npx skills add EveryInc/compound-engineering-plugin --skill ce-promote -g -a cursor -y`
Gemini CLI: `npx skills add EveryInc/compound-engineering-plugin --skill ce-promote -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add EveryInc/compound-engineering-plugin`

## Description

Draft launch or promotion copy for a shipped feature.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Promotion Copy

Turn a feature that just shipped into copy-pasteable, user-facing announcement copy, right inside the engineering workflow, so the messaging doesn't wait for a separate marketing pass.

**Done when:** every drafted channel is presented as a labeled, copy-pasteable block and the user has been offered a revision. **This skill drafts only, it never posts, publishes, schedules, commits, or opens PRs.** Posting is a human action.

It works **with or without Spiral**: with nothing installed it drafts directly from the editorial and social fundamentals in Path B (Direct drafting). When the Spiral CLI is present and authed, drafts come back voice-matched to the user's brand, an enhancement, never a requirement.

## Phase 1, Figure out what shipped

A free-form description in the arguments is the source of truth. Otherwise derive it from context, using what is available and never waiting on any single source:

- **Merged/active PR**, `gh pr view --json title,body,url` (the title and body usually state the user-facing value)
- **The diff**, `git diff main...HEAD --stat`, skimming notable changes so the claim is grounded in what actually changed
- **Changelog**, the top or `[Unreleased]` entry in `docs/changelog.md`, `CHANGELOG.md`, or similar
- **Recent commits**, `git log --oneline -15` for the arc of the change

Then write a 1-3 sentence summary of the **user-facing value**: what a user can now do that they couldn't before, and why they'd care. Outcome, not implementation, "You can now export any report to CSV in one click", not "Added a CsvSerializer and an export endpoint." If you can't confidently tell what shipped, ask one short question rather than guessing.

## Phase 2, Pick channels

The rest: https://github.com/EveryInc/compound-engineering-plugin/blob/HEAD/skills/ce-promote/SKILL.md