Splash Financial, US consumer-lending engineering team (current role)

Making agents useful for a whole team, not just me

role: Authored the team's shared agent skills; I maintain the engineering knowledge base.

// problem

One engineer getting faster with agents does not change how a team delivers. The team needed shared, repeatable skills and a common source of context that agents and people both read.

// approach

A test-plan runner skill that drives real staging environments through a browser and reports structured pass/fail results.
An end-to-end test writer skill that follows the house Playwright pattern.
An architecture-documentation skill.
The shared engineering knowledge base: architecture, service communication, schema and cross-repo patterns.
Spec-driven delivery: a cross-service bank-linking feature went through specify, plan, tasks and implement, with every ticket traced to a numbered task in a committed spec.

// architecture

Spec

Plan

Numbered tasks

Implement

engineers + agents

Knowledge base

Test-plan runner

staging, pass/fail

Review

A spec becomes a plan and numbered tasks. Engineers and agents implement against the tasks, using the shared knowledge base. The test-plan runner checks the result in staging and reports pass or fail before review.

// guardrails and production concerns

The test-plan runner reports structured pass/fail results, not prose.
Every ticket traces to a numbered task in a committed spec.
New tests follow one house pattern, whether a person or an agent writes them.

// outcome

Agent skills the whole team uses, and a delivery cycle where the committed spec, not a chat history, is the source of truth.

// stack

Claude Code
Agent skills
Playwright
Browser automation
Spec-driven development