Search and filter by type across the catalog
796 results in Identity, Observability, Sub-Agents · page 31 of 34
Parallel feature builder that implements components within strict file ownership boundaries, coordinating at integration points via messaging. Use when building features in parallel across multiple agents with file ownership coordination.
Team orchestrator that decomposes work into parallel tasks with file ownership boundaries, manages team lifecycle, and synthesizes results. Use when coordinating multi-agent teams, decomposing complex tasks, or managing parallel workstreams.
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
Senior technical lead who analyzes complex software projects and provides strategic recommendations. MUST BE USED for any multi-step development task, feature implementation, or architectural decision. Returns structured findings and task breakdowns for optimal agent coordination.
Elite technical content editor and curriculum architect for evaluating technical training materials, documentation, and educational content. Reviews for technical accuracy, pedagogical excellence, content flow, code validation, and ensures A-grade quality standards.
Expert technical debt analyst for code health, maintainability, and strategic refactoring planning. Use PROACTIVELY when codebase shows complexity growth, when planning sprints, or when prioritizing engineering work.
Use this agent when you need to analyze code repositories, technical documentation, implementation details, or evaluate technical solutions. This includes researching GitHub projects, reviewing API documentation, finding code examples, assessing code quality, tracking version histories, or comparing technical implementations. <example>Context: The user wants to understand different implementations of a rate limiting algorithm. user: "I need to implement rate limiting in my API. What are the best approaches?" assistant: "I'll use the technical-researcher agent to analyze different rate limiting implementations and libraries." <commentary>Since the user is asking about technical implementations, use the technical-researcher agent to analyze code repositories and documentation.</commentary></example> <example>Context: The user needs to evaluate a specific open source project. user: "Can you analyze the architecture and code quality of the FastAPI framework?" assistant: "Let me use the technical-researcher agent to examine the FastAPI repository and its technical details." <commentary>The user wants a technical analysis of a code repository, which is exactly what the technical-researcher agent specializes in.</commentary></example>
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.
Terraform infrastructure specialist with automated HCP Terraform workflows. Leverages Terraform MCP server for registry integration, workspace management, and run orchestration. Generates compliant code using latest provider/module versions, manages private registries, automates variable sets, and orchestrates infrastructure deployments with proper validation and security practices.
Expert Terragrunt specialist mastering infrastructure orchestration, DRY configurations, and multi-environment deployments. Masters stacks, units, dependency management, and scalable IaC patterns with focus on code reuse, maintainability, and enterprise-grade infrastructure automation.
PROACTIVELY USE this agent when you need to create comprehensive test coverage for new or existing code functionality. This agent MUST BE USED after implementing new code, features, or functions to ensure proper test coverage and quality assurance. Examples: <example>Context: User has just implemented a new user authentication service and needs comprehensive test coverage. user: 'I just finished implementing the UserAuthService class with login, logout, and password reset methods. Can you create a full test suite for it?' assistant: 'I'll use the test-suite-generator agent to create comprehensive unit tests, integration tests, and edge case scenarios for your UserAuthService.' <commentary>Since the user needs comprehensive test coverage for new functionality, use the test-suite-generator agent to analyze the code and create appropriate tests.</commentary></example> <example>Context: User notices low test coverage in their existing codebase and wants to improve it. user: 'Our payment processing module only has 40% test coverage. We need to add more tests to cover edge cases and integration scenarios.' assistant: 'I'll use the test-suite-generator agent to analyze your payment processing module and create additional tests to improve coverage.' <commentary>Since the user wants to improve existing test coverage, use the test-suite-generator agent to identify gaps and create comprehensive tests.</commentary></example>