Skip to content

Bring an existing product

Bring a shipping product when you already have something in production. GrowthOS grounds itself in what you ship today, then plans only what is next — not a full rewrite.

Three steps: Basics (name, one-liner, next-wave goal) → Add context (paste docs, or Connect coding agent with seed_product_context) → Review & save a living PRD (As-is plus next-wave REQs via upsert_living_prd). Then continue in Idea Lab for delivery phases and backlog of that wave only.

Do not ask MCP to generate a legacy rewrite backlog. Continue planning later adds another wave on the same project.

  • Paste a PRD, README, or architecture notes as product context.
  • Create a project shell and let a coding agent explore the repo (growthos-product-context skill).
  • Review the living PRD and next-wave requirements before Idea Lab.
  • Skip a greenfield rewrite of features you already ship.
  • Onboarding an existing codebase or product into GrowthOS.
  • Planning the next outcome (one concrete goal) on a shipping product.
  • A Planner seat.
  • For the agent path: a gos_ API key and the product-context skill in your coding agent.
  • /projects/new → Bring a shipping product
  • Direct: /projects/new?mode=existing
  1. Open /projects/new?mode=existing.
  2. Name the product, write a one-liner, and set one concrete What’s next goal.
  3. Paste docs, or Connect coding agent: create the project shell, run the Product Context skill in the repo.
  4. Review the generated product summary and next-wave requirements; regenerate if the goal is too broad.
  5. Save & continue in Idea Lab — delivery phases and backlog cover the next wave only.
  • The living PRD describes As-is plus a tight next-wave goal.
  • Idea Lab does not try to rebuild the entire existing product.
  • Tighten What’s next to one outcome before regenerating.
  • Agent explore needs the repo open locally plus GrowthOS MCP.
  • Pasting a huge dump with no next-wave goal.
  • Using seed_product_context to request a full rewrite backlog.