CUSTOM AI AGENTS · Product & engineering
Test writeras part of your team.
Identify behaviors. Write cases. Explain coverage and gaps.
Explore this agent for my team ↗01 · THE WORK, STEP BY STEP
How the task moves forward.
Agents work with project context, conventions and acceptance criteria. They prepare code, tests or documentation for the team's existing workflow.
- 01
Identify behaviors
Connects requirements to behavior that can be observed and checked.
- 02
Write cases
Prepares relevant normal and edge cases using the project's tools.
- 03
Explain coverage and gaps
Describes covered behavior and scenarios still needing definition.
02 · ILLUSTRATIVE EXAMPLE
A situation that may feel familiar.
An online shop covers discount rules and their edge cases.
Illustrative scenario, not a customer case study or measured results.
SlackExampleRead about the scope of the assignment at the team's channel.
JiraExampleRecord the known scope without marking the issue as resolved.
Error 403 when exporting orders
Leo · Support
- ✓Two people affected since this morning
- ○Locate the request and trace
- ○Check roles and permissions
GitHubExampleRead the trace. A 403 identifies the rejected request but does not yet establish its cause.
Error trace
Producción · Diagnóstico de solo lectura
GET /api/orders/export → 403request → requireAccess → ForbiddenErrorÚltimo evento: 10:38 · Personas afectadas: 2- ○Check the orders:export permission
- ○Check account access
JiraExampleLeave the investigation pending with evidence; do not change permissions to hide the error.
Check the export permission
Technical Officer
- ✓Request and trace linked
- ○Check affected roles against the access policy
- ○Validate a fix without granting improper access
SlackExampleShare the result and distinguish prepared work from executed work.
03 · YOUR WAY OF WORKING
Fits the business you already have.
Context and tools
We start with your current documents, systems and channels. We assess feasible connections and define the permissions required for this specific task.
Improves with your feedback
Approved corrections are incorporated into instructions, examples or knowledge sources. We review changes before expanding the agent’s scope.
A clear way to evaluate
We agree on a representative sample and measure review time, errors, exceptions and output quality against the current workflow. Feasibility is decided using that evidence.
04 · COMMON QUESTIONS
Before getting started.
What information does this agent need?
Specifications, code and testing tools. We review quality, currency and access before connecting the workflow. You do not need to replace all your tools to begin.
What will my team receive?
Proposed tests with documented scope. We agree on the format and delivery channel during setup, together with cases that need review.
Which decisions remain with people?
The team retains approval over changes, merges and deployments.
Can it coordinate with other agents?
Yes. We define what this agent hands to the next one and who handles exceptions. It can interact through Slack, WhatsApp, email or Microsoft Teams, depending on the integration and permissions we configure.
INDUSTRY APPLICATIONS
Where it could fit.
RELATED AGENTS
A team that works together.
Developer agent
Reviewable change before integration or deployment.
See tasks and example ↗Product & engineeringCode reviewer
Code review with justified observations.
See tasks and example ↗Product & engineeringBug triage assistant
Structured issue and technical context.
See tasks and example ↗START WITH ONE TASK
How would this fit your business?
Tell us how you do it today. We will define the scope, tools and controls with you.