Use this agent when you need to quickly locate relevant files across a large codebase to complete a specific task. This agent is particularly useful when:\n\n<example>\nContext: User needs to implement a new payment provider integration and needs to find all payment-related files.\nuser: "I need to add Stripe as a new payment provider. Can you help me find all the relevant files?"\nassistant: "I'll use the scout agent to quickly search for payment-related files across the codebase."\n<Task tool call to scout with query about payment provider files>\n<commentary>\nThe user needs to locate payment integration files. The scout agent will efficiently search multiple directories in parallel using external agentic tools to find all relevant payment processing files, API routes, and configuration files.\n</commentary>\n</example>\n\n<example>\nContext: User is debugging an authentication issue and needs to find all auth-related components.\nuser: "There's a bug in the login flow. I need to review all authentication files."\nassistant: "Let me use the scout agent to locate all authentication-related files for you."\n<Task tool call to scout with query about authentication files>\n<commentary>\nThe user needs to debug authentication. The scout agent will search across app/, lib/, and api/ directories in parallel to quickly identify all files related to authentication, sessions, and user management.\n</commentary>\n</example>\n\n<example>\nContext: User wants to understand how database migrations work in the project.\nuser: "How are database migrations structured in this project?"\nassistant: "I'll use the scout agent to find all migration-related files and database schema definitions."\n<Task tool call to scout with query about database migrations>\n<commentary>\nThe user needs to understand database structure. The scout agent will efficiently search db/, lib/, and schema directories to locate migration files, schema definitions, and database configuration files.\n</commentary>\n</example>\n\nProactively use this agent when:\n- Beginning work on a feature that spans multiple directories\n- User mentions needing to "find", "locate", or "search for" files\n- Starting a debugging session that requires understanding file relationships\n- User asks about project structure or where specific functionality lives\n- Before making changes that might affect multiple parts of the codebase

Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant code changes to ensure everything works as expected. Examples:\n\n<example>\nContext: The user has just finished implementing a new API endpoint and wants to ensure it works correctly.\nuser: "I've implemented the new user authentication endpoint"\nassistant: "Great! Now let me use the tester agent to run the test suite and validate the implementation"\n<commentary>\nSince new code has been written, use the Task tool to launch the tester agent to run tests and ensure everything works properly.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to check test coverage after adding new features.\nuser: "Can you check if our test coverage is still above 80%?"\nassistant: "I'll use the tester agent to analyze the current test coverage and provide a detailed report"\n<commentary>\nThe user is asking about test coverage metrics, so use the tester agent to run coverage analysis.\n</commentary>\n</example>\n\n<example>\nContext: After fixing a bug, ensuring the fix doesn't break existing functionality.\nuser: "I've fixed the database connection issue in the auth module"\nassistant: "Let me use the tester agent to run the test suite and ensure the fix doesn't introduce any regressions"\n<commentary>\nAfter bug fixes, use the tester agent to validate that existing tests still pass.\n</commentary>\n</example>