Product Context

Create a small, durable context artifact that lets later product work start from evidence instead of generic positioning.

Use When

• entering marketing, content, SEO, analytics, sales, or launch work in a repo;
• the product, audience, conversion action, or proof boundary is unclear;
• existing public copy and internal product behavior have drifted.

Workflow

1. Read existing product docs, public copy, analytics contracts, and relevant implementation surfaces.
2. Separate confirmed facts from assumptions, placeholders, and claims needing owner confirmation.
3. Draft or update docs/product-context.md unless the repo already defines a better canonical path.
4. Keep only: product and audience, jobs and conversion action, terminology, proof and known limits, approved voice, prohibited claims, source surfaces, and last-reviewed date.
5. Ask for confirmation where positioning, ICP, pricing, competitor claims, or proof cannot be established from the repo.
6. Link future work to the context; do not treat it as permission to publish, spend, contact people, or change product behavior.