Platform Team Service Catalogue Draft
Define what an internal platform offers teams.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Draft a service catalogue for an internal platform team. Engineering teams and their needs: [TEAMS_NEEDS]. Current tooling: [TOOLING]. Platform team size: [PLATFORM_TEAM_SIZE]. List services (for example CI templates, deploy pipeline, observability stack, secrets, databases, onboarding) each with a description, what is included, what is not, support level (self-service, best effort, on-call), request process, and a measure of success. Define principles (golden paths with escape hatches), an intake process, and a roadmap with criteria for what the platform will not build. Include a customer survey of ten questions to validate the catalogue and a way to measure adoption honestly. Close with risks: becoming a bottleneck, building unused features, and under-resourcing support. Add a template for a single service page with all the fields used in the catalogue, filled with one invented example. Include a plan for deprecating a service with notice periods and migration support, and a table of how to prioritise requests using impact, number of teams, and effort so that decisions are transparent to the engineering organisation.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Service: CI templates Includes: build, test, scan for 3 languages. Not included: custom pipelines for legacy apps. Support: self-service plus office hours Tuesday. Request: ticket form; response within 2 working days. Success measure: new service gets a working pipeline in under 1 hour. Service: Observability stack - dashboards, alerts, tracing starter. Support: best effort; on-call for the platform itself. Principles: golden paths with escape hatches. Out of scope: building one-off tools for a single team. Risks: becoming a bottleneck; unused features. Survey: 10 questions each quarter.
Illustrative only, made-up data. Your results will differ and must be reviewed.