I think a lot of folks ended up in a world where you write specs and designs in Markdown documents and use that to drive the outcome (the code, the system, test

I think a lot of folks ended up in a world where you write specs and designs in Markdown documents and use that to drive the outcome (the code, the system, tests, etc). So you drive intend through those specifications and design docs. Lately though, I've switched tact a bit and have resurrected some ~20yr old research called Behaviour Tree Engineering or Behaviour Trees, so I'm now writing specifications called BT specs. e.g: https://bte.mills.io/s/v4Mjbyf0OBJWm5YRLwG5XiIH https://bte.mills.io/s/v4Mjbyf0OBJWm5YRLwG5XiIH