Explore a repo for product context
Overview
Section titled “Overview”Use growthos-product-context when the repo is the source of truth. The agent explores the tree, calls seed_product_context, and upserts a living PRD. You then plan one next wave in Idea Lab — never a full rewrite backlog.
Who / time / plan
Section titled “Who / time / plan”- Who: Engineer onboarding a shipping product into GrowthOS
- Time: Part of existing-product setup — not a 15-minute sprint claim
- Plan: Needs a
gos_key. Free allows one MCP handoff; Pro+ unlimited. Still next-wave only.
What you can do here
Section titled “What you can do here”- Seed as-is product context from a local or cloned repo.
- Correct invented architecture before you approve the living PRD.
When to use
Section titled “When to use”- Path B (
/projects/new?mode=existing) and docs paste is weaker than the code.
Prerequisites
Section titled “Prerequisites”- Repo access in the agent workspace plus a
gos_key. - A one-sentence next-wave goal already written in Basics.
Where to find it
Section titled “Where to find it”/projects/new?mode=existingthen connect agent.- API Keys & Agents → product-context SKILL.md.
Step-by-step
Section titled “Step-by-step”- Create the existing-product project and write the next-wave goal.
- Load
growthos-product-context. Point the agent at the repo. - Let it
seed_product_contextandupsert_living_prd. Review every invented claim. - Continue in Idea Lab for that wave only.
What success looks like
Section titled “What success looks like”- Living PRD matches the repo well enough to plan the next wave.
Tips & best practices
Section titled “Tips & best practices”- Paste docs instead when the repo is huge and you only have a one-pager.
Common mistakes
Section titled “Common mistakes”- Prompting “generate the complete remaining backlog for this SaaS”.