devops-engineer

abakhru

Designs and implements CI/CD pipelines, infrastructure automation, container orchestration, environment management, and observability. Use when setting up or improving CI/CD pipelines, writing infrastructure as code (Terraform, Pulumi), configuring Docker/Kubernetes, managing environments, setting up monitoring/alerting, or automating any infrastructure or deployment workflow.

api-contract-test-engineer

abakhru

Covers REST and GraphQL API testing (status codes, schemas, edge cases, auth), contract testing with Pact for service-to-service boundaries, and service virtualization/mocking strategy. Use when writing API tests, setting up contract tests between services, designing mocking strategy for dependencies, or reviewing API test coverage.

test-automation-architect

abakhru

Designs and owns the test automation framework, folder structure, tooling decisions, CI/CD integration, and shared infrastructure (fixtures, page objects, API clients, helpers). Use when setting up a test framework from scratch, evaluating or changing test tools, configuring CI pipelines for test execution, or reviewing framework-level changes.

product-manager

abakhru

Expert product manager that frames problems, writes crisp PRDs with testable acceptance criteria, scores and prioritizes features (RICE/MoSCoW), defines success metrics and instrumentation requirements, and produces structured handoffs to engineering, design, and QA. Use when defining a new feature, writing a spec, building a roadmap, prioritizing a backlog, or answering "what should we build and why?"

backend-python

abakhru

Modern Python backend stack: FastAPI, SQLAlchemy 2.0, Pydantic v2, uv, ruff. Use when: building Python APIs, async services, or working with Python backend code. Triggers: "fastapi", "python backend", "sqlalchemy", "pydantic", "uv", "ruff", "python api", "async python".

exploratory-test-engineer

abakhru

Explores any application — UI, API, mobile, or codebase — to discover and document all features, behaviors, edge cases, and risks. Produces a feature map, session notes, and specialist handoff packages that feed the rest of the QA team. Use when mapping an unknown or undocumented application, discovering implicit features, generating input for test strategy, or when "we don't know what we don't know."