Initialize product

Initialize Product

Build a compact source of truth that every other workflow can read without rediscovering the project.

Workflow

1. Inspect repository guidance, package manifests, product UI, landing pages, store copy, analytics, billing, release assets, and existing strategy documents.
2. Confirm <repo-root> is the intended existing repository, then run scripts/init_product_context.py <repo-root> to create missing context files. The script never replaces existing files.
3. Populate the files from evidence. Mark inferred statements as Assumption and missing decisions as Unknown.
4. Keep each fact in one canonical file according to references/context-contract.md.
5. Add links rather than duplicating long explanations across files.
6. Record the initialization decision and known gaps in docs/product/decisions.md.

Required context

• brief.md: problem, product, capabilities, constraints
• audience.md: segments, jobs, pains, buying context
• positioning.md: category, alternatives, differentiation, claims
• brand.md: voice and visual direction
• competitors.md: alternatives and evidence
• seo-strategy.md: organic acquisition direction
• content-plan.md: editorial backlog and cadence
• launch-plan.md: release channels and readiness
• sales.md: offer, objections, conversion assets
• metrics.md: funnel definitions and available data
• roadmap.md: prioritized outcomes
• decisions.md: dated decisions, assumptions, and reversals

Quality bar

• Do not expose secrets or copy environment values.
• Do not convert marketing claims into facts without evidence.
• Preserve useful existing documents and user edits.
• Match the user's language for prose while keeping filenames stable.