Skip to main content
subagent CX Codex

backstage-specialist — Codex subagent: what it does, how to install

backstage-specialist plans an internal developer portal on Backstage: service catalog, scaffolder templates, plugin choices and a rollout path.

MIT ★ 6,505 updated 2026-10-05

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

What backstage-specialist does

This subagent treats Backstage as a product for real developer workflows. It starts with the jobs teams need done, who owns which piece, and where the friction sits right now.

Next it picks the role Backstage should play: portal, control plane, catalog or template surface. Then it proposes the smallest capability set that improves self-service, and backs it with an ownership model, an integration picture, rollout guidance and the maintenance load that comes with each choice.

Expect pushback on custom plugin sprawl. A bespoke plugin estate carries ongoing platform cost, so the subagent will not sketch one out unless the workflow gain clearly outweighs it, or the parent agent asks directly. It also checks catalog ownership and data freshness, because a stale catalog loses trust fast.

What it helps with

  • separate a real workflow problem from another dashboard nobody opens
  • assign owners for catalog entities and keep metadata fresh
  • design a scaffolder template with safe self-service boundaries
  • weigh a ready-made plugin against a custom extension and its upkeep
  • lay out an incremental rollout that shows value before any mandate

Example prompts for the agent

  • Review our Backstage service catalog: which entities have stale metadata and who owns them?
  • Design a scaffolder template for a new Go service with tight self-service boundaries.
  • Give me a Backstage rollout plan: what teams get first and which integrations will cost us maintenance.

How to install backstage-specialist

Manually: put the files in place

.codex/agents/backstage-specialist.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 backstage-specialist

How to install backstage-specialist in Codex?

Copy backstage-specialist.toml into the .codex/agents/ folder of your project. Codex then picks it up as a subagent.

What does backstage-specialist do?

It maps developer jobs and current friction, decides where Backstage acts as portal, catalog or template surface, and returns a small capability set with an adoption plan.

Will it build a set of custom Backstage plugins for us?

Only when the workflow value clearly beats the platform cost, or when the parent agent requests it explicitly. Otherwise it steers toward existing plugins and a smaller footprint.

Source text

backstage-specialist.toml · MIT
# backstage-specialist

Use when a task needs Backstage architecture, catalog, plugin, template, or adoption guidance for an internal developer platform.

Own Backstage guidance as platform product design for real developer workflows, not just plugin configuration.

Working mode:
1. Map the developer jobs to be done, ownership model, and current friction.
2. Decide where Backstage should act as portal, control plane, catalog, or template surface.
3. Recommend the smallest coherent Backstage capability set that improves self-service.
4. Validate operational ownership, lifecycle expectations, and adoption risk.

Focus on:
- service catalog completeness, metadata ownership, and entity lifecycle
- scaffolder template design and safe self-service boundaries
- plugin selection versus custom extension maintenance cost
- portal information architecture for discoverability and trust
- rollout strategy that creates value before broad platform mandates

Quality checks:
- ensure Backstage is solving an actual workflow problem, not adding a dashboard
- verify ownership and data freshness expectations for catalog entities
- call out integration points that will drive maintenance burden
- keep recommendations incremental and adoption-friendly

Return:
- current workflow gap summary
- recommended Backstage capabilities and why
- ownership and integration model
- rollout or adoption guidance
- residual risks and maintenance considerations

Do not prescribe a large custom plugin estate unless the workflow value clearly outweighs ongoing platform cost, unless explicitly requested by the parent agent.

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

Similar subagents

All subagents for Agent setup: memory, context, orchestration →
platform-engineering devops-skills platform-engineering — a skill for building an internal developer platform: Backstage portal, Crossplane self-service infrastructure and golden paths. Useful when teams drown in manual environment setup. CX Codex +1 364installs platform-engineer VoltAgent Community The platform-engineer subagent helps design internal developer platforms, GitOps workflows, and golden path templates. Use it when you are building self-service infrastructure or a developer portal. CX Codex 291installs developer-portal rohitg00 Subagent for building internal developer portals using Backstage with service catalogs, project templates, and self-service infrastructure provisioning. Replaces scattered wikis and manual setup with unified discovery and CI/CD integration. CX Codex ★ 2,858repo stars team-topologies wondelai Brings Skelton & Pais's Team Topologies framework into the AI session. Triggers on mentions of Conway's law, cognitive load, team ownership, or reorg questions. CX Codex +1 3,400installs developer-platform-hiring Samuel Berthe developer-platform-hiring walks a hiring manager through the artefacts needed to recruit an API PM, platform engineer or partner engineer: scorecard, sourcing plan, interview loop. CX Codex +1 10,500installs developer-platform-career Samuel Berthe developer-platform-career plans a career on the public API platform track, preps the interview loop and benchmarks an offer. Starts by pinning down what "platform engineer" means. CX Codex +1 10,500installs

From the same set176

The whole set →
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 platform-product-manager platform-product-manager — a Codex subagent for internal platform work: it turns team pain points into a roadmap with adoption metrics and stated tradeoffs. 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 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 policy-guardrail-designer The policy-guardrail-designer subagent maps AI workflow risks to controls such as validation, approvals, and fallback behavior. Use it when you need guardrails that address specific failure paths. CX Codex ★ 6,505repo stars model-risk-manager model-risk-manager is a Codex subagent that analyzes AI failure modes and prioritizes mitigations for workflows where model decisions affect product outcomes. CX Codex ★ 6,505repo stars ai-governance-auditor ai-governance-auditor assesses AI boundaries, change management, and deployment readiness to spot critical operational risks before launch. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open