.claude/product-marketing-context.md

• Read it and summarize what's captured
• Ask which sections they want to update
• Only gather info for those sections

1. Auto-draft from codebase (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.
2. Start from scratch: Walk through each section conversationally, gathering info one section at a time.

1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
2. Draft all sections based on what you find
3. Present the draft and ask what needs correcting or is missing
4. Iterate until the user is satisfied

1. Briefly explain what you're capturing
2. Ask relevant questions
3. Confirm accuracy
4. Move to the next

• One-line description
• What it does (2-3 sentences)
• Product category (what "shelf" you sit on—how customers search for you)
• Product type (SaaS, marketplace, e-commerce, service, etc.)
• Business model and pricing

• Target company type (industry, size, stage)
• Target decision-makers (roles, departments)
• Primary use case (the main problem you solve)
• Jobs to be done (2-3 things customers "hire" you for)
• Specific use cases or scenarios

• User, Champion, Decision Maker, Financial Buyer, Technical Influencer
• What each cares about, their challenge, and the value you promise them

• Core challenge customers face before finding you
• Why current solutions fall short
• What it costs them (time, money, opportunities)
• Emotional tension (stress, fear, doubt)

• Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
• Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
• Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
• How each falls short for customers

• Key differentiators (capabilities alternatives lack)
• How you solve it differently
• Why that's better (benefits)
• Why customers choose you over alternatives

• Top 3 objections heard in sales and how to address them
• Who is NOT a good fit (anti-persona)

• Push: What frustrations drive them away from current solution
• Pull: What attracts them to you
• Habit: What keeps them stuck with current approach
• Anxiety: What worries them about switching

• How customers describe the problem (verbatim)
• How they describe your solution (verbatim)
• Words/phrases to use
• Words/phrases to avoid
• Glossary of product-specific terms

• Tone (professional, casual, playful, etc.)
• Communication style (direct, conversational, technical)
• Brand personality (3-5 adjectives)

• Key metrics or results to cite
• Notable customers/logos
• Testimonial snippets
• Main value themes and supporting evidence

• Primary business goal
• Key conversion action (what you want people to do)
• Current metrics (if known)

Target companies: Decision-makers: Primary use case: Jobs to be done:

Use cases:

Core problem: Why alternatives fall short:

Key differentiators:

• "[verbatim]" How they describe us:
• "[verbatim]" Words to use: Words to avoid: Glossary: | Term | Meaning | |------|---------| | | |

"[quote]" — [who] Value themes: | Theme | Proof | |-------|-------| | | |

• Show the completed document
• Ask if anything needs adjustment
• Save to

  .claude/product-marketing-context.md

• Tell them: "Other marketing skills will now use this context automatically. Run

  /product-marketing-context

  anytime to update it."

• Be specific: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"
• Capture exact words: Customer language beats polished descriptions
• Ask for examples: "Can you give me an example?" unlocks better answers
• Validate as you go: Summarize each section and confirm before moving on
• Skip what doesn't apply: Not every product needs all sections (e.g., Personas for B2C)