Ask-First: Mandatory Pre-Implementation Workflow

A pre-implementation workflow guides you through interrogating requirements, generating black-box tests first via a separate agent, and then implementing code to make those tests pass. This ensures clarity and correctness before any feature code is written.

The best way to prevent misunderstandings during refactoring is a deep requirement interrogation phase that clarifies system contracts and potential issues. This precedes test generation and implementation to ensure all stakeholder expectations are aligned.

Black-box test generation in TDD works by dispatching a separate agent to write failing tests based solely on requirement interrogations, without viewing the underlying implementation. This ensures test integrity and uncovers hidden assumptions before development starts.

Yes, this pre-implementation workflow specifically covers domain-specific considerations for RC racing simulation physics and behavior. It guides you through clarifying suspension physics requirements and generating tests for vehicle behavior under various conditions.

A separate agent should write tests to preserve black-box test integrity and uncover hidden assumptions. By not having the implementer write the tests, you reduce bias and ensure the tests accurately reflect interrogated requirements rather than implementation constraints.

The mandatory pre-implementation testing requires completing requirement interrogation and full black-box test generation before any implementation code is written. This strict three-phase process may introduce overhead for trivial bug fixes or rapid prototyping scenarios where immediate code changes are preferred.