Prompt
Need a prompt registry with comments and approvals
Latest observation
Oct 21, 2026
OpenAI APIWeb search: off
Here’s a practical prompt registry template you can use, with comments, versioning, and approvals built in.
Prompt Registry
1) Registry Purpose
A central place to store, review, approve, and track prompts used by your team.
2) Recommended Fields
| Field | Description |
|---|---|
| Prompt ID | Unique identifier |
| Prompt Name | Human-readable name |
| Owner | Person responsible for the prompt |
| Purpose | What the prompt is for |
| Prompt Text | Full prompt content |
| Model / Use Case | Which model or workflow it’s for |
| Status | Draft / In Review / Approved / Deprecated |
| Version | Version number |
| Created Date | When it was added |
| Last Updated | Last modification date |
| Comments | Reviewer notes / feedback |
| Approval Status | Pending / Approved / Rejected |
| Approved By | Approver name |
| Approved Date | Approval timestamp |
3) Example Registry Table
| Prompt ID | Prompt Name | Owner | Purpose | Version | Status | Comments | Approval Status | Approved By | Approved Date |
|---|---|---|---|---|---|---|---|---|---|
| PR-001 | Support Reply Draft | Alex | Draft customer support replies | v1.0 | Approved | Needs tone check for edge cases | Approved | Jamie | 2026-10-20 |
| PR-002 | Sales Outreach | Priya | Generate outbound sales emails | v0.9 | In Review | Add compliance disclaimer | Pending |
4) Suggested Workflow
Draft
- Prompt author creates or edits the prompt
- Add purpose, intended use, and version
Review
- Reviewer leaves comments directly in the registry
- Questions:
- Is the prompt clear?
- Does it produce consistent output?
- Any policy/compliance concerns?
- Are examples needed?
Approval
- Approver marks:
- Approved
- Rejected
- Needs changes
- Record approver name and date
Publish
- Move approved prompt into active use
- Lock or archive prior versions
5) Comment Format
Use a structured comment format to keep reviews consistent:
Comment fields
- Comment ID
- Prompt ID
- Reviewer
- Comment
- Severity: Low / Medium / High
- Resolution: Open / Resolved / Won’t Fix
- Date
Example
| Comment ID | Prompt ID | Reviewer | Comment | Severity | Resolution | Date |
|---|---|---|---|---|---|---|
| C-001 | PR-001 | Jamie | Add an example for refund requests | Medium | Resolved | 2026-10-20 |
| C-002 | PR-002 | Taylor | Remove phrasing that may violate policy | High | Open | 2026-10-21 |
6) Approval Template
You can attach this to each prompt record:
Approval Record
- Prompt ID:
- Version:
- Reviewed By:
- Approval Decision:
- Notes:
- Approved By:
- Approval Date:
7) Simple Google Sheets / Airtable Structure
If you want this in Sheets or Airtable, use tabs like:
- Prompts
- Comments
- Approvals
- Versions
- Archive
8) JSON Example
If you want a machine-readable registry:
{
"prompt_id": "PR-001",
"name": "Support Reply Draft",
"owner": "Alex",
"purpose": "Draft customer support replies",
"version": "1.0",
"status": "Approved",
"prompt_text": "You are a support assistant...",
"comments": [
{
"comment_id": "C-001",
"reviewer": "Jamie",
"comment": "Add an example for refund requests",
"severity": "Medium",
"resolution": "Resolved",
"date": "2026-10-20"
}
],
"approval": {
"decision": "Approved",
"approved_by": "Jamie",
"approved_date": "2026-10-20"
}
}
If you want, I can also create this as:
- a Google Sheets template,
- an Airtable base structure, or
- a Markdown/Notion template.