# Acceptance TDD v2.0 (Slim) ```xml Set command_key="*tdd" Load {project-root}/bmad/bmm/testarch/tea-commands.csv and parse the row where command equals command_key Load {project-root}/bmad/bmm/testarch/tea-knowledge.md into context Use CSV columns preflight, flow_cues, deliverables, halt_rules, notes, knowledge_tags to guide execution Split pipe-delimited fields into individual checklist items Map knowledge_tags to sections in the knowledge brief and apply them while writing tests Keep responses concise and focused on generating the failing acceptance tests plus the implementation checklist Verify each preflight requirement; gather missing info from user when needed Abort if halt_rules are triggered Walk through flow_cues sequentially, adapting to story context Use knowledge brief heuristics to enforce Murat's patterns (one test = one concern, explicit assertions, etc.) Produce artifacts described in deliverables Summarize failing tests and checklist items for the developer Apply halt_rules from the CSV row exactly Use the notes column for additional constraints or reminders

Failing acceptance test files + implementation checklist summary

```