Skip to content

Prompt: Create a New Product

Retired 2026-07-27 — per ADR-0017, this repository no longer scaffolds products. A new product is created entirely inside its venture's own implementation repository, following that repository's own conventions (see templates/implementation-repository/AGENTS.md's "Product registration" section for what every venture's implementation repository is expected to do: a product.json per product, kept in sync with this repository's portfolio/product-registry.json table of contents). scripts/create_product.py is retained but non-functional for its original purpose (its template source, ventures/<slug>/products/_template/, no longer exists in any venture) — do not use it. This file is kept for historical reference; do not follow the checklist below.

Role (historical)

You are guiding the creation of a new product within an existing venture, following that venture's products/README.md (or ventures/_template/products/README.md as the pattern) and portfolio/intake-and-stage-gates.md.

Objective (historical)

Scaffold a new product correctly, only once it has genuinely been approved for specification work — not simply because someone had an idea.

Checklist (historical — superseded, see note above)

  1. Confirm the product has cleared intake. Verify the product idea has been evaluated against portfolio/prioritization-framework.md and explicitly approved to proceed to specification work. If this hasn't happened, stop and raise it rather than scaffolding anyway.
  2. Confirm the slug and venture. Agree on [venture-slug] and [product-slug]; confirm the parent venture already exists and is registered (or explicitly confirm it's acceptable to proceed under an unregistered venture, if that's the deliberate situation).
  3. Run the scaffolding script. Use scripts/create_product.py to create ventures/[venture-slug]/products/[product-slug]/ from the appropriate template (the venture's own richer template if it has one, e.g. Digital Products, otherwise the generic template under ventures/_template/products/_template/).
  4. Fill in the product brief first. Complete product-brief.md before moving to product-requirements.md or deeper specification documents.
  5. Do NOT auto-register. Do not add the product to portfolio/product-registry.json as part of scaffolding unless explicitly requested — registration reflects a deliberate approval decision, matching the intake process.
  6. Report back. Summarize what was created, what's filled in vs. still placeholder, and confirm registration status explicitly.

Report an issue about this page