Tdd Pipeline

Write all tests before any implementation. Save them to the appropriate test files in the project.

• Test behavior, not implementation details
• Cover the happy path, edge cases, and error conditions from the plan
• Tests should be runnable now (they will fail — that is expected)

3. Implement via haiku-coder

Invoke the haiku-coder agent. Pass it explicitly:

• The full plan from step 1
• The test file paths (or full test content) from step 2
• All existing source files it will need to read to understand context
• A clear instruction: "implement the code to make these tests pass"

Do not summarize or abbreviate the plan when passing it — haiku-coder has no prior context.

4. Review

Once haiku-coder returns, review its output in the current conversation (where you have full context):

• Confirm the tests pass (check haiku-coder's reported results)
• Check for security issues, over-engineering, or missed edge cases
• Apply minor fixes directly
• If the implementation needs significant rework, invoke haiku-coder again with specific, targeted feedback on what to fix