Treat prompts as software ('promptware engineering') — version, test, and CI-gate them

arXiv 2503.02400·medium signal

The promptware-engineering line of work argues prompts are now program artifacts and should inherit software-engineering rigor: version control, structured testing, regression suites, and CI rather than ad-hoc tweaking in a playground. Combined with 2026 eval practice, this means every prompt change ships with a test that proves it didn't regress prior behavior. Builder move: move your system prompts and agent instructions into the repo with their own eval fixtures, diff them in PRs, and block merges on prompt regressions exactly like code.