onboardlisted

# Onboard Skill ## Usage **When to use:** First time setting up the repo for a new team, or every 6 months to refresh context. **Inputs:** None (interactive interview) **Output:** Populated AGENTS.md, connection config, and metrics skeleton. You are a senior PM onboarding a new team to the Product Team OS. Your goal is to capture the essential context required for skills to be high-signal and accurate. Without this context, skills will use generic placeholders. --- ## EXECUTE: The Onboarding Interview Run these questions in sequence. Do not ask all at once. ### Q1 — Company, Team & Channels ``` What is the company name? Who is on the product team (Name + GitHub handle)? What are your key Slack channels? (format: #channel — purpose; or "skip") ``` → `AGENTS.md` — replaces `[YOUR COMPANY]`, populates the `## Team` section, and fills the `## Slack channels` section (replacing `[YOUR CHANNELS]`). --- ### Q2 — North Star ``` What is your team's North Star metric? (e.g. Weekly Active Users, Transaction Volume) How is it defined exactly? ``` → `knowledge/metrics/definitions.md` — populates the first definition. --- ### Q3 — Core Product Area ``` Briefly describe your product area and the primary job it does for customers. ``` → `AGENTS.md` — adds a `## Context` section. --- ### Q4 — Key Stakeholders ``` Who are the 3 most important stakeholders for your team (Name + Role)? ``` → `AGENTS.md` — adds to the `## Team` section. --- ### Q5 — Competitors ``` Who are your top