# Workflow

## Code Changes

Before making any changes, outline your approach in 3-5 numbered steps. Include which branch you'll work on, what commands you'll run, and what success looks like. Wait for approval before starting.

## Response Style

When listing items (PRs, functions, optimization targets), provide the complete list ordered by priority on the first attempt. No partial lists.

## Commands

Long-running commands (benchmarks, profiling, optimizers) always run in the foreground. Do not use background processes.

## Debugging

When claiming something is a pre-existing issue (e.g., test failures on main), verify by checking out main and running the tests before making that claim.
