coding-workflow

TDD-minded test planning involves selecting appropriate vertical slices for testing. You choose unit test runners for logic, pgTAP for database logic, or agent-browser for UI visual validation, ensuring you write only the necessary tests.

Hypothesis-driven debugging involves forming a specific assumption about the bug's source, then using temporary logging to verify it. This method provides pragmatic guardrails to avoid fragile changes and isolate issues quickly.

Yes, you can use agent-browser for visual validation when adding small UI features to a React or Next.js app. It serves as an optional validation tool to verify visual tweaks after implementing the smallest coherent change.

For small-to-medium feature changes, you need enough test coverage to validate a TDD-minded vertical slice. This pragmatic approach ensures you satisfy requirements for minimal viable changes without introducing unnecessary or fragile tests.

You should reconsider minimal viable changes when your task falls outside small-to-medium feature changes, UI validations, or test selection. This approach is designed to simplify specifications, not to handle large-scale architectural rewrites.