Take a feature from problem to a design ready for engineering
Most design work stalls between "I have an idea" and "here's what to build," not at the sketching.
- Outcome
- A design that's been checked against the real problem, stress-tested for edge cases, and is specific enough for engineering to build from without guessing.
- Time
- 1-2 hours across sessions
This workflow is part of PromptKit Pro
A handful of prompts and workflows stay free for everyone — Pro unlocks the full library, including this one, plus the guided runner.
Design work often stalls in the gap between a rough idea and something engineering can actually build, because the intermediate steps — confirming the design solves the stated problem, checking it against edge cases, specifying states precisely enough — get skipped in favor of jumping straight to polished mockups of the happy path. This playbook runs those intermediate steps explicitly, so what reaches engineering is actually complete.
When not to use this
For a trivial UI tweak with no real ambiguity, this process is overkill — just make the change. This is for a feature substantial enough that skipping these steps would mean engineering hits real gaps later.
Did this work?
Engineering can pick up the design and start building without a round of clarifying questions about basic states and edge cases.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.