12:00 · Agent · design the solution

Design the solution

Feed the sharp Pain Card to a reusable Solution Architect agent. It explores broadly, then returns one buildable recommendation.

The Agent is the architect — not necessarily the answer. The recommended solution might be a setting, a saved prompt, an existing tool, an automation, an agent or a new workflow.

Three steps

01Feed one sharp Pain Card to the Painkiller Solution Architect.
02Let it ask no more than three questions, then explore three genuinely different solution routes.
03Choose one recommendation and leave with a Build Brief. Do not build it yet.

Explore before you commit

Configure or borrow
use what exists
An approved tool, setting or existing agent already solves enough. Configure the missing context or last mile.
Automate or upgrade
change existing work
Keep the job, remove manual steps or create a distinctly better output.
Invent
new job, new output
Create a capability that was never practical before. Use only when the pain actually demands it.

Score each route out loud: Value · effort · risk · dependencies

Painkiller Solution Architect

Use these instructions to create one reusable agent in your approved AI environment. After that, every new Pain Card becomes its input.

The architect explores and recommends. Cowork builds.

Create the reusable agent

You are the Painkiller Solution Architect. Your job is to turn one sharp Pain Card into the smallest useful AI-enabled solution. Process: 1. Restate the pain in one sentence. Do not solve a different problem. 2. Ask no more than three questions about the trigger, user, current process, evidence of success and non-negotiable boundaries. 3. Explore three genuinely different routes: - configure or borrow an approved tool or existing agent; - automate or upgrade work that already exists; - invent a new workflow only if the first two routes are insufficient. 4. Compare the routes on value, effort, risk and dependencies. 5. Recommend one route and explain why it is the smallest useful move. 6. Produce a Build Brief with: - Pain - Recommended solution - User and trigger - Inputs - Steps - Output - Evidence of success - Boundary - Human check - Smallest test today Do not build the solution. Stop and ask for approval of the Build Brief.

The prompt

Here is my Pain Card. Run the Painkiller Solution Architect process. Ask no more than three questions, explore three solution routes, recommend the smallest useful move and return one Build Brief. Do not build it yet.

Need a nudge?

What evidence would prove the pain moved?
What already exists that might solve enough?
What must never happen without a human?

Build Brief

Seven lines out of the architect. Stays in this browser — nothing here is sent anywhere.

Pain

Is this Build Brief sharp enough to build?

0 answersconnecting…

The solution we are taking forward…

Optional. Keep it non-sensitive — no customer names, no confidential detail. Nothing appears publicly until JJ approves it.

A sharp Build Brief beats a clever idea you cannot execute.