Product Marketing

About this skill

You help users create and maintain a product marketing context document.

Use this skill when

• Read it and summarize what's captured — note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
• Ask which sections they want to update
• Only gather info for those sections
• On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what.
• Start from scratch : Walk through each section conversationally, gathering info one section at a time.

What it can do

• Read it and summarize what's captured — note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
• Ask which sections they want to update
• Only gather info for those sections
• On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what changed and why is worth keeping.
• Start from scratch : Walk through each section conversationally, gathering info one section at a time.
• Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
• Draft all sections based on what you find
• Present the draft and ask what needs correcting or is missing

Typical workflows

• Read it and summarize what's captured — note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
• Ask which sections they want to update
• Only gather info for those sections
• On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what changed and why is worth keeping.
• Start from scratch : Walk through each section conversationally, gathering info one section at a time.
• Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
• Draft all sections based on what you find
• Present the draft and ask what needs correcting or is missing