| name | pm-os-onboarding |
| description | Interactive setup for PM-Operating-System in Codex. Use when the user says "onboard", "PM-OS setup", "set up PM-OS", or asks to configure this repo for a Codex or dual-runtime workflow. |
PM-OS Onboarding
Run an interactive setup flow for PM-Operating-System inside Codex. Collect the user's answers, write config/pm-os-config.yaml, and run the setup script for the selected runtime.
When to use
- "onboard"
- "PM-OS setup"
- "set up PM-OS"
- "configure this repo"
- "set this up for Codex"
Workflow
- Confirm the goal:
- Explain that you will gather the user's PM context, update
config/pm-os-config.yaml, and run ./scripts/setup.sh.
- Explain that the Codex path can generate repo-scoped skills plus
.codex/config.toml.
- Ask for runtime preference:
- Default to
codex.
- If the user wants to preserve Cursor too, choose
both.
- Ask whether Codex skills should stay repo-scoped only or also install to the user skill directory.
- Ask the setup questions in small batches:
- Company name and role title first.
- Product name and product type.
- Managers, VIPs, org structure.
- Quarterly goals and deprioritization signals.
- Domain context.
- Tool usage.
- Slack and Google Drive details only if those tools are enabled.
- Skills and agent toggles if the user wants customization; otherwise keep defaults from the config template.
- After collecting company and role:
- Offer to research the company before continuing.
- If the user wants that context, use web research directly or follow the
company-researcher workflow if it is available.
- Summarize the company context in 1-2 short paragraphs and continue onboarding.
- Write
config/pm-os-config.yaml:
- Include the new
runtime block with primary and codex_install_scope.
- Preserve the existing config structure and boolean values.
- Run setup from the repo root:
- For Codex only:
./scripts/setup.sh --runtime codex --codex-scope <repo|user>
- For dual runtime:
./scripts/setup.sh --runtime both --codex-scope <repo|user>
- If the user explicitly wants Cursor only, use
./scripts/setup.sh --runtime cursor.
- Close with next steps:
- Point the user to
knowledge/ to customize strategy docs.
- Remind them that Codex project context lives in
PM-OS-AGENTS.md.
- Remind them that Codex MCP config lives in
.codex/config.toml.
- Mention the v1 limitation:
continual-learning remains Cursor-only / experimental for Codex.
Output requirements
- Keep the conversation interactive and concise.
- Parse natural-language answers into structured YAML cleanly.
- Do not depend on Cursor-only agent tools or file formats.
- If a value is unknown, use the repo template default rather than inventing details.
