TeamEngineering · v1.1.0

DevOps & SRE Team

CI/CD, infrastructure as code, observability and SLOs, incident command and release management, with runbook and 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.

Agents 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.

Commands 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.

What this team will not do

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.

€59one-time

→ Colleagues

Also worth hiring

All teams →
Team

Migration & SEO Team

Replatforming that keeps the traffic: migration architecture, platform engineers for Shopify, WordPress/WooCommerce and PrestaShop/Magento, technical SEO, content and URL mapping, analytics and Search Console continuity, and international SEO.

8 agents · 3 skillsEngineering · v1.1.0
€89incl. VATvs €60k / month on payroll
Team

Product Engineering Team

A full software team — architecture, backend, frontend, database, code review and QA — with design-doc and code-review workflows.

6 agents · 2 skillsEngineering · v1.1.0
€59incl. VATvs €45k / month on payroll
Team

Security & AppSec Team

Defensive security — threat modelling, secure code review, supply chain risk, incident response and SOC 2 / ISO 27001 / NIS2 / DORA mapping.

5 agents · 2 skillsEngineering · v1.1.0