Overview
Before step 1 of 5
You will leave with a pattern you can justify to a teammate and a short list of avoid-this anti-patterns.
The pattern picker — You have a real task and need a defensible pattern choice.
You have a real task and need a defensible pattern choice.
Path position
The pattern picker: You have a real task and need a defensible pattern choice.
This is inferred from the page and path structure. Nothing is saved as completion state.
Begin path
Walk the decision heuristic
Always start by asking whether you need an agent at all. The heuristic forces that question.
Start step 1Steps
Walk the decision heuristic
Always start by asking whether you need an agent at all. The heuristic forces that question.
You should be able to state the first question of the heuristic and what 'no' to it implies.
Scan the catalogue
See the full design space before deciding — the cheapest pattern often beats the cleverest.
You should be able to name two patterns you would not have picked before scanning and why they now look plausible.
Routing as the typical first reach
Most real tasks decompose into 'which kind of question is this'. Routing is usually the right starting shape.
You should be able to describe a task routing fits and a task it does not.
When one node isn't enough
If routing can't carry the work, an orchestrator with worker specialists usually can. It is the next step up in complexity.
You should be able to name one signal in your real task that pushes past 'routing' into 'orchestrator-workers'.
Avoid these before committing
Pattern selection without anti-pattern awareness is half a decision. The six anti-patterns are the most expensive ways the choice goes wrong.
You should be able to name the anti-pattern most likely to apply to the pattern you just picked.