Loading…
Loading…
Product work goes wrong quietly. A spec that sounds complete but never says what happens on failure, a roadmap that lists everything and commits to nothing, an MVP that is just the full thing with the timeline halved. The prompts below are built to surface those gaps early. They make the model separate what is known from what is assumed, name the riskiest belief rather than the longest list, and give a recommendation with a reason attached. Use them on a request you were handed this morning, a backlog you have been avoiding, or a launch you are three weeks from.
36 prompts in 4 groups
Turning a vague request into something a team can build: specs, PRDs, stories and acceptance criteria.
Deciding what makes the cut and what the plan actually is: backlogs, MVPs, estimates, roadmaps.
Checking the idea before you commit: research, feedback, competitors, risky assumptions, success metrics.
Getting a release out and told: launch plans, go / no-go, release notes, deprecations, post-launch retros.
Send a prompt you keep coming back to. A person reads every one.
Suggest a prompt