Hi HN, I'm Yousef. I've built a lot of agents for vertical AI startups in the past few years, and I've become convinced that prompts are code, so must be kept in git.
The startups that decouple do so because engineers build agents with git, and non-engineers (lawyers/clinicians/etc) align agents outside of git.
So the problem of coordination and versioning shifts to out-of-sync docs and platforms.
This is why I built Gravel.
An open-source library that embeds a prompt editor straight into your app. Your prompts have a single source of truth (your codebase).
After a minute of setup:
1. Your team can make prompt PRs without knowing what a PR is
2. They can review outputs straight from your production traces
3. Those reviews create prompt change suggestions and evals
If you're building vertical agents, would love your feedback on it!
0 comments
—
Show HN: Gravel – allow non-engineers to make prompt PRs · HackerTrans
The startups that decouple do so because engineers build agents with git, and non-engineers (lawyers/clinicians/etc) align agents outside of git.
So the problem of coordination and versioning shifts to out-of-sync docs and platforms.
This is why I built Gravel.
An open-source library that embeds a prompt editor straight into your app. Your prompts have a single source of truth (your codebase).
After a minute of setup:
1. Your team can make prompt PRs without knowing what a PR is
2. They can review outputs straight from your production traces
3. Those reviews create prompt change suggestions and evals
If you're building vertical agents, would love your feedback on it!