press-release — Claude Code skill: press release before code
Writes an Amazon-style press release for a product that does not exist yet. The point is to settle what customers get before anyone starts building.
npx skills add deanpeters/Product-Manager-Skills --skill press-release -a claude-codeWhat press-release does
The skill walks the agent through Amazon's Working Backwards method: draft the announcement first, build second. The structure is fixed. Ten parts, from a benefit-led headline and dateline to the customer problem, the outcome-based solution, a leader quote, a company blurb and a media contact. The full skeleton sits in template.md.
Steps run in order, each with its own quality check. The headline has to name the benefit for the customer, not the feature list. The author budgets 30-45 minutes and asks for the idea plus who it serves. When that context is missing, the skill points to sibling skills in the same repository: proto-persona, problem-statement, positioning-statement. So you may need two or three other skills filled in first, or the draft stays vague.
It is a planning document, not launch copy. Writing it after the product ships is too late, and the author advises against using it on small tweaks.
What it helps with
- state the customer value before a spec line is written
- get stakeholders to agree on what the launch actually promises
- kill a weak idea by trying to announce it
- fill a ten-part press release structure without gaps
- test whether a feature earns a mention in the announcement
Example prompts for the agent
- press-release: offline note editor for long train rides, audience is people working on the move
- Use the press-release skill for auto-picking recipes from what is already in the fridge
- press-release, the problem is manual sprint reports, audience is team leads
How to install press-release
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill press-release -a claude-code2Manually: put the files in place
~/.claude/skills/press-release/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/press-release/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill press-release -a codex2Manually: put the files in place
.agents/skills/press-release/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill press-release -a cursor2Manually: put the files in place
.cursor/skills/press-release/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills press-release2Manually: put the files in place
.github/skills/press-release/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill press-release -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/press-releaseManually: put the files in place
.devin/skills/press-release/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill press-release -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about press-release
How do I install press-release in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill press-release -a claude-code. The skill lands at ~/.claude/skills/press-release/SKILL.md.
What does press-release do?
It drafts a customer-facing announcement of an unbuilt product across ten sections, with a quality check at every step. Teams use it to pressure-test an idea before engineering starts.
When should I skip press-release?
On small tweaks, and once the product is already built. It is a planning artifact, not final launch copy.