Skip to content

Onboard an existing SaaS

Existing product is Path B. You name the product and one next-wave goal, then either paste docs or connect a coding agent to explore the repo (seed_product_context) and upsert a living PRD (upsert_living_prd). Idea Lab then plans that wave only.

GrowthOS will not generate a full rewrite backlog from MCP. If you need a greenfield PRD, use Path A instead.

  • Who: Team that already ships a product
  • Time: 1–2 hours for living PRD + next-wave start
  • Plan: Any plan that can create a project (Free = 1 project). Sprints still Pro+.
  • Paste existing docs (PRD, README, support notes) into the wizard.
  • Or run the product-context skill so an agent seeds the living PRD.
  • Continue in Idea Lab for the next wave: phases, UX Spec, wave backlog.
  • The product already has users. You want the next slice planned in GrowthOS.
  • You do not want to pretend the current system does not exist.
  • A next-wave goal you can say in one sentence.
  • Docs to paste, or a repo + gos_ key for agent explore.
  • /projects/new?mode=existing
  • Product-context SKILL.md on API Keys & Agents.
  1. Open /projects/new?mode=existing. Fill Basics: name and next-wave goal.
  2. Paste docs, or connect a coding agent and run explore / seed_product_context.
  3. Review the living PRD (upsert_living_prd). Correct anything the agent invented.
  4. Continue in Idea Lab for this wave only: phases → UX Spec skip-or-not → wave backlog.
  5. On Pro+, plan and start a sprint from that wave backlog.
  • A living PRD describes as-is product plus one next wave.
  • Backlog items belong to the wave, not a full rewrite.
  • Prefer agent explore when the repo is the source of truth; paste when docs are. See Explore a repo for the skill loop.
  • Asking the agent to dump every feature as backlog.
  • Starting a second project instead of Continue planning for wave two.