TeamEngineering · v1.1.0

DevOps & SRE Team

CI/CD, Infrastructure as Code, Observability und SLOs, Incident Command und Release-Management, mit Runbook- und Incident-Response-Workflows.

CI/CD, infrastructure as code, observability, incident command and releases.

/incident runs the live response in the right order — declare, assign roles, establish impact, ask what changed, mitigate before understanding — and afterwards writes the blameless postmortem with dated, owned actions.

Agenten 5

  1. 01cicd-engineerUse for build and delivery pipelines — CI configuration, test stages, artifact building, deployment automation, caching and pipeline performance, and making a slow or flaky pipeline trustworthy again.
  2. 02incident-commanderUse during and after production incidents — coordinating response, structuring investigation, deciding on mitigation versus root-cause fixing, communicating status, and running the postmortem.
  3. 03infrastructure-engineerUse for infrastructure as code and cloud architecture — Terraform and similar tooling, networking, container orchestration, scaling, cost optimisation and environment management.
  4. 04observability-engineerUse for monitoring and alerting — metrics, logs, traces, SLOs and error budgets, dashboards for on-call, and fixing alert fatigue.
  5. 05release-managerUse for releases — versioning, release notes, change management, deployment planning and sequencing, feature flags, rollback plans and go/no-go decisions.

Skills 2

  1. 01incident-responseRun a production incident and its postmortem — declaration, roles, mitigation, communication cadence, stand-down criteria and a blameless postmortem with dated actions. Use during an outage or when writing up one afterwards.
  2. 02runbookWrite an operational runbook that someone unfamiliar can follow at 3am — symptoms, checks, decisions, actions, verification and escalation. Use when asked to document an operational procedure, an on-call guide, or what to do when an alert fires.

Befehle 2

  1. 01/incidentRun a live incident — roles, impact, hypotheses, mitigation and communication — or write the postmortem for one.
  2. 02/pipelineBuild or fix a CI/CD pipeline — stages, caching, artifacts, environments, deployment strategy and a tested rollback.

Was dieses Team nicht tut

It will not put secrets in pipelines, logs or image layers; apply to production without a reviewed plan; deploy a destructive migration alongside the code that depends on it; page anyone for something with no available action; or name individuals in a postmortem. It will tell you when the honest fix is deleting two-thirds of your alerts, or when the pipeline is fine and the test suite is the problem.

59 €einmalig

→ Kollegen

Ebenfalls einstellenswert

Alle teams →
Team

Migration & SEO Team

Replatforming, das den Traffic behält: Migrationsarchitektur, Plattform-Engineers für Shopify, WordPress/WooCommerce und PrestaShop/Magento, technisches SEO, Content- und URL-Mapping, Analytics- und Search-Console-Kontinuität, internationales SEO.

8 Agenten · 3 SkillsEngineering · v1.1.0
89 €inkl. MwSt.statt 60.000 € / Monat Lohnkosten
Team

Product Engineering Team

Ein komplettes Software-Team — Architektur, Backend, Frontend, Datenbank, Code Review und QA — mit Design-Doc- und Code-Review-Workflows.

6 Agenten · 2 SkillsEngineering · v1.1.0
59 €inkl. MwSt.statt 45.000 € / Monat Lohnkosten
Team

Security & AppSec Team

Defensive Sicherheit — Threat Modelling, sicheres Code Review, Supply-Chain-Risiko, Incident Response und Mapping auf SOC 2 / ISO 27001 / NIS2 / DORA.

5 Agenten · 2 SkillsEngineering · v1.1.0