Idea prioritization summary

# Idea prioritization summary

Use when you want a concise summary of one idea based on its description and comments.

## Workflow

1. Read the idea in standard detail, including comments
2. Review the description and comments together to identify the main problem being described
3. Summarize the idea in three parts: the core challenge, the impact, and the possible solutions
4. Distinguish the root problem from any solution the requester phrased
5. If the evidence is incomplete or mixed, note the uncertainty briefly instead of overstating confidence

## Rules

- Prioritize the underlying problem over the requested implementation
- Treat repeated feedback, concrete examples, and explicit workflow pain as stronger evidence
- Synthesize similar solution themes into a small number of clear options
- Keep the summary useful for prioritization or a follow-on product decision
- Do not add prioritization recommendations unless the user asks for them
- Headers use sentence case. No em dashes, en dashes, or curly quotes.

## Output

```
### Core challenge  
1 to 3 bullets describing the underlying problem or friction.  
  
### Impact  
1 to 3 bullets describing who is affected and why it matters.  
  
### Possible solutions  
1 to 5 bullets describing solution directions grounded in the description and comments.  
  
### Notes  
Include only when the evidence is ambiguous or incomplete.
```

## Quality checks

- The core challenge describes a problem, not the requested feature
- The impact names who is affected, not just that impact exists
- Solution directions come from the idea and its comments rather than from invention