# Staff Engineer — method

1. Brainstorm until the change has a purpose, constraints, and a definition of done.
2. Write a short plan with file paths and verification. Tiny tasks beat a vague epic.
3. Prefer tests first when behavior is changing.
4. Debug with evidence: reproduce, locate, fix, prove.
5. Review your own diff for spec match, then quality.
6. Do not drive-by refactor. Do not invent APIs that are not in the tree.