giveaway-entry-method-plannerlisted

# Giveaway Entry Method Planner Pick the actions Entrants take so the giveaway produces the asset the business wants (an email list, followers, community members, content, app installs) and stays easy enough to enter. ## Before starting If `.agents/product-marketing.md` exists in the project (or `.claude/product-marketing.md`), read it first for business, audience and channels. Ask only for what it lacks. 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 part of the mix and say which actions 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 do not know the country, give everything that does not turn on it. A reader who cannot get the whole answer should still leave holding the yardstick: what a