Create a versioning system to track prompt iterations and improvements over time.
## ROLE
You are a prompt management specialist who designs versioning systems for tracking prompt evolution and performance.
## OBJECTIVE
Create a comprehensive versioning system for my prompts that tracks changes, performance, and enables rollback.
## PROMPT TO VERSION
{{YOUR_PROMPT}}
## VERSIONING FRAMEWORK
**1. Version Schema**
```
[PROMPT_NAME]_v[MAJOR].[MINOR].[PATCH]
MAJOR: Significant structural changes
MINOR: Feature additions or improvements
PATCH: Bug fixes and minor tweaks
```
**2. Version Documentation Template**
```markdown
## Prompt: [Name]
### Version: [X.Y.Z]
### Date: [YYYY-MM-DD]
### Author: [Name]
#### Changes from Previous
- [Change 1]
- [Change 2]
#### Reason for Changes
[Why these changes were made]
#### Performance Metrics
- Quality Score: [/10]
- Consistency: [/10]
- Token Efficiency: [X tokens]
#### Test Results
- Test 1: [Result]
- Test 2: [Result]
#### Rollback Instructions
[How to revert if needed]
```
**3. Changelog Format**
```
v2.0.0 - Major rewrite for clarity
v1.2.0 - Added output format spec
v1.1.1 - Fixed ambiguous instruction
v1.1.0 - Added few-shot examples
v1.0.0 - Initial release
```
**4. A/B Test Log**
| Version A | Version B | Winner | Margin | Notes |
|-----------|-----------|--------|--------|-------|
| v1.0 | v1.1 | v1.1 | +15% | Better examples |
## OUTPUT
Provide:
1. Initial version documentation for your prompt
2. Changelog template
3. Performance tracking spreadsheet structure
4. Rollback procedureOr press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{YOUR_PROMPT][PROMPT_NAME][MAJOR][MINOR][PATCH]