Onboarding your team

The fastest way to get your team onto the platform is the Nomos Agent — your self-serve interface to the osinfra.io platform. Tell it what your team needs and it opens a pull request with every change. No local setup, no YAML to write by hand.

Ready to go?

You have your team's details and want to build a prompt to paste straight into the Nomos Agent.

Build your agent prompt →

How it works

📋

1. Collect your details

Gather your team key, display name, description, GitHub usernames, and admin email before you start.

💬

2. Build your prompt

Use the prompt builder below, then paste the generated text straight into the Nomos Agent.

🚀

3. Merge and go live

The agent opens a pull request. Once it merges, your GCP folder, identity groups, and GitHub team are created automatically.

Before you start

To onboard your team, the Nomos Agent needs a small set of details. Have these ready before you invoke it.

Filter:✓ Required (6)

▸datadog_team_membershipsobjectrequired

Datadog team memberships. admins manage the team; members have read-only access.

display_namestringrequired

Team display name. Title Case; spaces and the lowercase word "and" are allowed.

display_name_commentstringrequired

Inline comment rendered after display_name in the tfvars file. Used for the team etymology blurb. Also used as the `description` frontmatter on the team's docs index page; render_team_docs_index and open_team_docs_pr require this field to be non-empty — an empty string will produce a docs_input_invalid error.

▸github_parent_team_membershipsobjectrequired

GitHub team membership. maintainers have admin rights on the team; members have read access.

▸google_basic_groups_membershipsobjectrequired

Google Cloud Identity basic groups: admin, reader, writer.

team_typestringrequired

Team Topologies type. Must match the team_key prefix.

"platform-team""stream-aligned-team""complicated-subsystem-team""enabling-team"

Build your agent prompt

You have all the details

Fill in the form, hit Copy, then paste the result into the Nomos Agent. The agent will confirm each detail and open a pull request on pt-logos. Toggle Optional above to reveal additional fields — the filter bar is shared with the section above.

Filter:✓ Required (4)

General

Team key

Team key. Must match the team_type prefix scheme: pt- (platform), st- (stream-aligned), ct- (complicated-subsystem), et- (enabling).

Display name

Team display name. Title Case; spaces and the lowercase word "and" are allowed.

GitHub

Maintainers required

GitHub parent team memberships. All team members should be listed here. Use GitHub usernames (NOT email addresses).

Datadog

Admin email required

Datadog team memberships. admins manage the team; members have read-only access. Also becomes the owner of the Google Cloud Identity admin group.

Generated prompt

Onboard a new team.


Maintainers: (required)

How to invoke the agent

💻

Copilot CLI

From a terminal, clone the agents repo and run the Copilot CLI:

git clone https://github.com/osinfra-io/pt-techne-agents
cd pt-techne-agents
gh copilot

Type /agent, select Nomos Agent, and paste your prompt.

🌐

GitHub UI

Navigate to pt-techne-agents/agents on GitHub, select the Nomos Agent, and paste your prompt. The agent opens a PR automatically.

🤖

VS Code

Open pt-techne-agents in VS Code, start a Copilot Chat session, type /agent, select Nomos Agent, and paste your prompt.

GitHub MCP — configuration required

The agent opens pull requests and reads repository state using the GitHub MCP server. It must be enabled with write toolsets.

Configure the GitHub MCP server with a fine-grained Personal Access Token scoped to the osinfra-io organization with the following permissions:

Permission	Access
Contents	Read and write
Issues	Read and write
Pull requests	Read and write
Workflows	Read and write

Fine-grained PATs are created at github.com/settings/personal-access-tokens/new. Set the resource owner to the osinfra-io organization.