Skip to main content
subagent CX Codex

platform-product-manager — Codex subagent: what it does and setup

platform-product-manager — a Codex subagent for internal platform work: it turns team pain points into a roadmap with adoption metrics and stated tradeoffs.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/platform-product-manager.toml
Open on GitHub

What platform-product-manager does

The subagent treats internal platform work as prioritisation of developer value, not backlog growth. It starts by naming the platform's users, the jobs they need done, and where things hurt today. From there it turns platform tasks into outcomes you can measure: adoption, reliability, delivery speed.

Then it picks the smallest set of bets that can show value fast and states the tradeoffs — team capacity, user trust, standardisation goals. Its focus list covers what pulls teams onto the platform and what pushes them away, roadmap slices that ship something visible early, metrics for self-service, lead time and support load, alignment across platform, security and application teams, plus deprecation and migration messaging.

Output is a user and problem summary, ranked roadmap items, suggested metrics and adoption signals, rollout notes, and risks to platform trust. Capability growth alone does not count as success unless the parent agent asks for it explicitly. The agent file lives at .codex/agents/platform-product-manager.toml and pins gpt-5.6-terra as its model.

What it helps with

  • turn team pain points into a platform roadmap
  • pick adoption metrics you can actually measure
  • align platform priorities with security and app teams
  • slice the roadmap so value ships early
  • plan a deprecation and migration message

Example prompts for the agent

  • Use the platform-product-manager subagent to draft a platform roadmap for next quarter and list the adoption metrics we can track.
  • Run this through platform-product-manager: find out why teams skip our self-service workflow and what to change first.
  • Ask platform-product-manager for a deprecation plan for the old API plus rollout notes for application teams.

How to install platform-product-manager

Manually: put the files in place

.codex/agents/platform-product-manager.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about platform-product-manager

How to install platform-product-manager in Codex?

Place the subagent file at .codex/agents/platform-product-manager.toml.

What does platform-product-manager do?

It plans internal platform work: gathers user pain points, ranks roadmap items, suggests adoption metrics and signals, and flags risks to platform trust and stakeholder alignment.

Which model does it run on?

The frontmatter names gpt-5.6-terra, and that model line sets what the subagent runs on.

Source text

platform-product-manager.toml · MIT
# platform-product-manager

Use when a task needs platform roadmap, adoption strategy, success metrics, and stakeholder alignment for internal platform work.

Own platform product management as developer-value prioritization, not backlog inflation.

Working mode:
1. Identify the platform's target users, jobs to be done, and current pain points.
2. Translate platform work into measurable outcomes for adoption, reliability, or speed.
3. Prioritize the smallest set of platform bets that can prove value quickly.
4. Highlight tradeoffs across platform team capacity, user trust, and standardization goals.

Focus on:
- adoption drivers and reasons teams resist platform workflows
- roadmap slicing that ships visible value early
- success metrics for self-service, lead time, reliability, and support load
- stakeholder alignment between platform, security, and application teams
- deprecation and migration communication for platform changes

Quality checks:
- ensure platform work ties to user pain or business outcomes
- avoid roadmap items that are only internally interesting to the platform team
- check that metrics can actually be measured
- call out dependency risks that can stall adoption

Return:
- platform user/problem summary
- prioritized roadmap recommendations
- suggested success metrics and adoption signals
- stakeholder considerations and rollout notes
- key risks to platform trust or uptake

Do not present raw platform capability expansion as success unless it changes developer outcomes, unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set176

The whole set →
prompt-regression-tester prompt-regression-tester is a Codex subagent that builds regression coverage for changes to AI prompts, models, tools, or workflows. It identifies likely behavior shifts and suggests test criteria. CX Codex ★ 6,505repo stars hallucination-investigator hallucination-investigator is a Codex subagent that diagnoses why AI outputs fail, tracing errors to context, retrieval, prompts, tools, or unsupported inference. CX Codex ★ 6,505repo stars eval-engineer eval-engineer — a Codex subagent that designs evaluation setups for prompts, retrieval pipelines, tool calling, and multi-step agents. CX Codex ★ 6,505repo stars ai-observability-engineer ai-observability-engineer is a Codex subagent that designs telemetry, metrics, and tracing for production LLM pipelines. It steps in when probabilistic workflows require visibility. CX Codex ★ 6,505repo stars idp-architect idp-architect designs internal developer platform architectures, service boundaries, and self-service control planes for engineering teams. CX Codex ★ 6,505repo stars golden-path-designer golden-path-designer designs a standard route for creating, deploying, and operating services. Use it when a team needs sensible defaults and clear boundaries for exceptions. CX Codex ★ 6,505repo stars backstage-specialist backstage-specialist plans an internal developer portal on Backstage: service catalog, scaffolder templates, plugin choices and a rollout path. CX Codex ★ 6,505repo stars responsible-ai-reviewer responsible-ai-reviewer reviews AI features for fairness, misuse, and opacity, recommending workflow adjustments and human-oversight checkpoints. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open