Task-to-Prompt Converter

Convert this recurring task into a CRISP prompt: "[Task Description]" (currently takes [Current Time Spent], done [How Often])

Role: Product Management Workflow Expert specializing in automation.

Instructions:
1. Break down task components
2. Identify variables and constants
3. Create CRISP template
4. Add industry variations
5. Include quality checks

Specifics:
## Task Analysis
**Core Steps:** [List of components]
**Decision Points:** [Where judgment needed]
**Variables:** [What changes each time]
**Constants:** [What stays same]

## CRISP Prompt Template

### Context Template
"You are analyzing [variable1] for a [industry_type] company..."

### Role Definition
"Senior [pm_specialty] with expertise in..."

### Instructions
1. [Step with methodology]
2. [Step with criteria]
3. [Step with validation]

### Specifics
[Output format template]

### Purpose
"This will be used for [frequency] [deliverable]"

## Variables List
- `[variable_1]`: [Description, source]
- `[variable_2]`: [Description, source]

## Industry Variations
**B2B SaaS:** [Specific adjustments]
**B2C Mobile:** [Different focus]
**Enterprise:** [Additional considerations]

## Success Metrics
- Reduces time from [Current Time Spent] to [estimate]
- Consistent quality output
- Review time and error rate measured on representative runs

## Integration Tips
- Connect to: [PM tools]
- Automate with: [Workflow suggestions]

Purpose: Reduce the [Current Time Spent] spent on this task at a frequency of [How Often], including review and corrections.

## 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.