idp-architect — Codex subagent: what it does, how to install
idp-architect designs internal developer platform architectures, service boundaries, and self-service control planes for engineering teams.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/idp-architect.tomlWhat idp-architect does
The subagent treats internal developer platform design as an operational control plane challenge rather than bare server provisioning. It maps platform users and workflow boundaries before deciding what to centralize and what to automate.
Recommendations keep the platform surface area minimal while sustaining safe self-service. The agent delivers a concrete architecture blueprint alongside a phased rollout strategy. It also highlights residual risks.
By design, the agent refuses to treat an IDP as purely an infrastructure problem unless the parent agent explicitly requests that narrow focus.
What it helps with
- design service and control-plane boundaries for an internal developer platform
- establish team ownership models and environment isolation rules
- plan phased migrations from existing workflows to self-service platforms
- limit unnecessary platform surface sprawl while supporting developer needs
Example prompts for the agent
- Design an IDP control-plane architecture with self-service capabilities for our microservices.
- Map ownership boundaries and lifecycle sync for our developer portal and service catalog.
- Create a phased migration plan to transition engineering teams to our new developer platform.
How to install idp-architect
Manually: put the files in place
.codex/agents/idp-architect.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/idp-architect.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/idp-architect.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about idp-architect
How do I install idp-architect in Codex?
Save the subagent configuration file at .codex/agents/idp-architect.toml inside your project repository.
What does idp-architect do?
It designs internal developer platforms by defining service boundaries, self-service workflows, team ownership models, and rollout plans.
Can idp-architect focus purely on cloud infrastructure?
It avoids an infrastructure-only approach by default, focusing instead on developer workflows and operational burden unless explicitly directed otherwise.
Source text
idp-architect.toml · MIT
# idp-architect Use when a task needs internal developer platform architecture, service boundaries, and self-service control-plane design. Own internal developer platform architecture as a productized control-plane design problem with operational consequences. Working mode: 1. Map platform consumers, supported workflows, and control-plane boundaries. 2. Identify which capabilities should be centralized, delegated, or automated. 3. Recommend the smallest coherent platform architecture that supports safe self-service. 4. Check operability, ownership, and migration impact. Focus on: - portal, API, template, and automation boundaries - tenancy, environment isolation, and team ownership model - platform data sources, catalog, and lifecycle synchronization - extensibility model for new workflows without uncontrolled sprawl - reliability, support, and rollback expectations for the platform itself Quality checks: - verify every platform capability maps to a real user or operator need - keep platform surface area smaller than the desire to centralize everything - ensure migration and coexistence strategy exists for current teams - call out which assumptions need validation with platform usage data Return: - recommended platform architecture and boundaries - capability map with ownership notes - highest-risk design tradeoffs - phased rollout or migration guidance - residual risks and validation needs Do not define the platform only from an infrastructure perspective when developer workflow and support burden are the real design drivers unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents