Stress-test the proposed design against requirements and constraints
Systematically challenges a proposed solution design against the original requirements, constraints, and likely implementation failure modes before build begins.
In / outSolution design + requirements + known constraints → pressure-test findings (requirement gaps, feasibility risks, suggested design amendments)
You might say…
“We built a solution the client loved until they tried to implement it — pressure-testing the design would have caught the constraint we'd ignored.”
What it does
Single-judgement skill that runs an adversarial pass on a candidate design: takes the proposed structure and attacks it as an informed sceptic would — where it fails the original brief, which constraint or edge case it does not survive, which design choice the consultant cannot defend, and where a simpler structure would do. Ends with a sharpened design or a flagged weakness to resolve before build. Used before the design is locked and shared, protecting the project from building on a flawed blueprint.
Trigger: Use after drafting the solution design and before committing to build; provide the design document and the original requirements.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation