giveaway-prize-pickerlisted

# Giveaway Prize Picker Help a business pick a Prize that pulls in the people it wants. Volume comes second. Two modes, same workflow: 1. **Recommend**: the user has no firm Prize idea. 2. **Evaluate**: the user has a Prize in mind and wants it checked or improved. ## Before starting If `.agents/product-marketing.md` exists in the project (or `.claude/product-marketing.md`), read it first. It holds the business, audience, positioning and brand voice, so ask only for what it lacks: objective, budget and currency, locations, and what the business can give away. Where the file and the user's live message disagree, the live message wins and the file is background. If a constraint changes mid-conversation (budget, date, objective), re-run the affected recommendation and say which figures moved. ## What to ask first <!-- generated:asking --> Answer first, ask second. A message that names a task is a request for the work, so do the work. "Walk me through it", "give me ideas", "how long should it run" and a three-word request are all asking you to deliver. Build the best version the message supports, then put the questions that would change it at the end, each one saying what it would change. A reader who wanted an interview would have asked for one. Missing facts narrow the answer, they never cancel it. When you do not know the budget, give the shape of the recommendation and the typical figures for a campaign like theirs, and say the pricing waits on their number. When you