
Use Notion as the primary interface for repository architecture, pipelines, modules, constants, plans, todos, issues, and commit logs. Use when Codex needs to create or update a repo-backed Notion board, answer questions from board contents, keep repo-derived content synced one-way from the repo into Notion, or save the board location locally without exposing that state in git.
Prepare an "ask an expert" handoff bundle: a pasteable prompt.md plus a context.zip containing the minimum repo files needed for a grounded second opinion from an external assistant (e.g., ChatGPT Pro / GPT-5.2 Pro). Use only when the user explicitly asks to "use Oracle", "ask ChatGPT Pro", "ask an expert", or "get a second opinion". Never include secrets (.env, keys, credentials) in the bundle.
Coordinate a Codex multi-agent step workflow from a repo-local Markdown plan file. Use when the request names a Markdown plan path in the target repo, explicit step IDs or ranges such as 3-5,7, and asks the main agent to track plan state while worker and reviewer subagents loop until each step is approved, committed, and written back.