SRE Agent Planner

An assistant-agnostic, open-source planning template that helps you make the right decisions before you deploy an Azure SRE Agent.

You point your AI assistant of choice (GitHub Copilot, Claude, ChatGPT, Gemini, etc.) at this repo, answer a short guided interview, and walk away with a written Adoption Constitution — an ADR-style decision record your team, platform owners, and advisors can agree on and act from.

The agent is quick to deploy. The decisions behind it — placement, identity, RBAC, model provider, cost, and how many agents — are architecture. This template makes you decide them on purpose.

Who it's for

• Owner / platform engineers planning their own SRE Agent rollout.
• Advisors / pre-sales / SREs running a structured discovery session with a customer.

Same interview, same output. The Adoption Constitution serves both as the agreed reference for the rollout.

What you get

• A facilitator prompt (instructions.md) that interviews you one decision at a time, explains trade-offs, recommends sensible defaults, and flags compliance/blast-radius traps.
• Small, on-demand context files (context/) so the assistant only loads what each decision needs — keeping the conversation cheap and focused.
• A fill-in Adoption Constitution template (templates/adoption-constitution.md) that becomes your decision record.
• A live visual report (templates/report/) — after each section the assistant updates a report.html that renders your decisions with real Azure service icons; sections you haven't reached show as in progress / pending.

How to use it

1. Clone or download this repo.
2. Open a chat with your assistant of choice in a way that lets it read these files (e.g. open the folder in an IDE with an AI assistant, attach the files, or paste their contents).
3. Give it instructions.md as the starting prompt (e.g. "Follow the facilitator instructions in instructions.md and begin.").
4. Answer the questions. The assistant pulls the relevant context/<topic>.md only when it reaches that decision. Each decision starts with plain-language context (what it is, why it matters, the options, the traps) before the question — and you can ask it to explain, give an example, or recommend at any point before you commit.
5. At the end, it produces your completed Adoption Constitution. Save it, review it with your owners, and use it to drive the actual deployment.

As you go, the assistant also keeps report.html up to date — open it in a browser for a visual, icon-rich summary of every decision so far (keep templates/report/theme.css alongside it; it's already in the cloned repo). Prefer a single portable file you can email or move anywhere? Ask for the standalone report and it'll use report-template-standalone.html, which inlines the theme so report.html needs no other files.

No installation, no dependencies, no vendor lock-in — it's just Markdown (the optional visual report is plain HTML/CSS).

See a complete worked example in example/ — an interview snippet, the resulting Adoption Constitution, and a finished report.html.

Repository layout

sre-agent-planner/
├── README.md                         # this file
├── instructions.md                   # the facilitator behaviour (start here)
├── context/                          # one small reference per decision area, loaded on demand
│   ├── segmentation.md
│   ├── placement-and-rbac.md
│   ├── identity-permissions.md
│   ├── run-modes.md
│   ├── model-provider-compliance.md
│   ├── pricing-aau.md
│   ├── connectors-and-knowledge.md
│   └── deployment-and-iac.md
├── templates/
│   ├── adoption-constitution.md      # the ADR-style output the interview fills in
│   └── report/                       # the live visual report system (deterministic)
│       ├── report-template.html      # shell copied to ./report.html (links the theme)
│       ├── report-template-standalone.html  # single-file variant (theme inlined, portable)
│       ├── components.html           # pre-built decision components (real Azure icons)
│       └── theme.css                 # the canonical report theme (don't recreate)
├── example/                          # a complete worked example (Payments spoke team)
│   ├── conversation.md               # interview snippet
│   ├── adoption-constitution.md      # the filled-in ADR output
│   └── report.html                   # the completed visual report (self-contained)
└── LICENSE

Credits & trademarks

The visual report references Azure architecture icons via the community benc-uk/icon-collection CDN. Azure service icons are trademarks of Microsoft; they're used here for identification in architecture-style diagrams only and do not imply endorsement. To self-host, download the official set from the Azure architecture icons page and repoint the icon URLs in templates/report/components.html.

Accuracy & disclaimer

This template encodes Azure SRE Agent behaviour as documented at the time of writing. Product details change — always confirm against the official documentation before deploying. In particular, pricing is expressed in Azure Agent Units (AAUs); confirm the current AAU-to-currency rate on the pricing page before building a business case. This project is community-maintained and not an official Microsoft product.

License

MIT — see LICENSE.