Michael Okafor

Answered What is a sane way to version prompts alongside application code?

Prompts in the repo, as files, versioned with the code. Hash the file contents and store the hash with every logged output. Then you can always tie an output back to the exact text that produced it, including for outputs generated six months ago by a prompt that no longer exists. We tried a database table so non-engineers could edit. It was a mistake — prompt changes are behaviour changes and they need review, staging and rollback, which is what the repo already gives you.

Shared a bide Plan a feature as commit-sized steps before an agent codes it

Have a coding agent plan before coding: assumptions, commit-sized steps with tests, a de-risking order, open questions and what's out of scope.