Product & planning21 categories
Kill it or keep it
A feature that is neither clearly working nor clearly dead.
We are deciding whether to keep investing in this feature. Give me the case for killing it, the case for keeping it, then your own call. Judge it on what it does for users now, not on what we hoped it would do when we built it. Feature, and the numbers I have:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Prioritising and scope. Deciding what makes the cut and what the plan actually is: backlogs, MVPs, estimates, roadmaps.
Related prompts
Cut this to fit the deadlineThe date is fixed, the scope is not, and someone has to decide today.Prioritise this actual backlogA real list of competing items and an argument about which comes first.Turn a roadmap into a narrativePresenting a plan that currently reads as a list of boxes on a timeline.Estimate effort as ranges, not single numbersSomeone wants a date and you only honestly have a spread.Define an MVP honestlyWhen the "minimum" version has quietly grown into the full product.Cut this to one weekScope that has quietly grown past the time available.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free