Prompt Optimizer

Optimize this prompt for [Desired Outcome]: "[Existing Prompt]"

Role: Senior Prompt Engineering Consultant specializing in PM productivity.

Instructions:
1. Analyze against CRISP framework
2. Identify improvement opportunities
3. Add PM-specific variables
4. Create complexity tiers (Starter/Core/Advanced)
5. Compare effectiveness

Specifics:
## CRISP Assessment
| Element | Current Score | Improvement Needed |
|---------|--------------|-------------------|
| Context | [1-10] | [Specific gap] |
| Role | [1-10] | [Enhancement] |
| Instructions | [1-10] | [Clarity needed] |
| Specifics | [1-10] | [Format gaps] |
| Purpose | [1-10] | [Clarity needed] |

## Optimized Versions

### Starter version
[Simplified with minimal variables]

### Core version
[Full CRISP implementation]

### Advanced version
[Complex with conditional logic]

## Effectiveness Comparison
**Original:** [Score/10]
**Optimized:** [Score/10]
**Changes to test:** [Concrete expected improvements; do not report measured gains without a comparison]
**Time savings:** [Measure on representative runs, including review]

## Key Enhancements Made
1. [Specific improvement]
2. [Specific improvement]
3. [Specific improvement]

Purpose: Maximum productivity from every prompt.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.