Implement With Validation

Contract

Browser-facing work is complete only when automated gates pass and every changed user journey passes in the real local application through the user's existing Chrome session.

REQUIRED SUB-SKILL: Use implement for test-first vertical slices and no-debt implementation.

REQUIRED BROWSER CAPABILITY: Use an available integration that can drive the user's existing Chrome session. In Codex, use chrome:control-chrome. In Claude Code, use a configured Chrome/browser integration or MCP with the same capability. Follow that integration's authentication and safety rules. If the runtime cannot control the existing Chrome session, report BLOCKED.

If the requested behavior has no browser-reachable journey, use implement instead.

Before Coding

Create a browser acceptance matrix from the requirements: