{ "schema": "aiblocks-page/1", "id": "agency-engineering-platform-engineer", "type": "agent", "name": "Developer platform designer", "summary": "Plan an internal developer platform with easy paths for new services, self-serve requests and adoption checks. Bring your team's pain points.", "headline": "Developer platform designer", "subhead": "Tell it where your developers lose time, such as waiting on tickets or setting up each new service by hand. It ranks what to fix first and designs a \"golden path\", one standard way to do the job. You get the path spec, the self-serve command, catalogue entries and adoption measures.", "job": { "id": "build-software", "name": "Build and ship software" }, "level": "intermediate", "thinking": "high", "tested": true, "updated": "2026-11-03", "first_published": "2026-10-26", "inputs": [ { "type": "question", "required": true, "label": "Question", "what": "the problem, decision or piece of work you want help with, and what a good outcome looks like" }, { "type": "source_text", "required": false, "label": "Source text", "what": "a long source in full: an article, a video or talk transcript, or notes from a book, with its title, author and link" } ], "outputs": [ { "type": "plan", "required": true, "label": "Plan", "what": "a dated plan: what to do, in what order, with a decision rule for each step" } ], "you_give": [ "A short list of what slows your developers down, such as tickets and wait times", "How many teams and services you have, and the main languages", "The tools you use today, such as your cloud, CI and Backstage (optional)", "The five requests the platform team gets most often", "Security or compliance rules every service must meet (optional)" ], "you_get": [ "A ranked list of what to pave first, with the reason for each", "A golden path spec for the top item, with its inputs, defaults and outputs", "A design for the self-serve command or form", "A service catalogue entry with owner, on-call and runbook", "Adoption and developer experience measures, with starting targets", "A rollout and retire plan, and the open questions" ], "use_when": [ "Developers wait on tickets for databases, domains, secrets or deploy setup.", "Every new service is set up differently, and no one knows which way is right.", "You are setting up Backstage or a service catalogue and need a plan for it.", "You built platform tools and want to know if teams use them." ], "skip_when": [ "You need one build and deploy pipeline for one project. Use the Deployment pipeline designer.", "You need to keep a live service up, with alerts and recovery goals. Use the Site reliability engineer.", "You are designing the structure of a single app. Use the Software architect." ], "output_sample": { "input": [ "A short list of what slows your developers down", "The five requests your platform team gets most often", "Your teams, services, languages and tools", "Security or compliance rules (optional)" ], "prerequisites": [ "An AI that can read pasted text or files, such as Claude, ChatGPT or Gemini", "A way to ask developers what annoys them, such as a short survey (optional)" ], "output": [ { "name": "Friction list", "contains": "Each manual task, how often it happens, what it costs and who does it today." }, { "name": "Paved or dirt roads", "contains": "Each workflow marked supported, unsupported or missing, with a priority rank." }, { "name": "Golden path spec", "contains": "The inputs, defaults and outputs of the top path, with the trade-off behind each default." }, { "name": "Self-serve interface", "contains": "The command or form developers use, with its options and an override file." }, { "name": "Catalogue entry", "contains": "Owner, on-call, runbook and dependencies for a service." }, { "name": "Measures", "contains": "Adoption and developer experience measures with starting targets, and how to count them." }, { "name": "Rollout plan", "contains": "The pilot, launch note, adoption review and the rule for retiring or rebuilding a path." } ] }, "output_shape": "FRICTION LIST\n | |