Skills / pick-gtm-agent-pattern
Most agents are over-built — an orchestrator-worker mesh doing a job a plain pipeline would do better.
pick-gtm-agent-pattern runs the gate sequence that picks an agent's build pattern and forces the "patterns NOT used" list — so over-engineering dies in planning, before a line of code is written.
Point it at a new agent idea, a workflow you want to turn into an agent, or an existing agent you suspect is over-built. It fills an intake block from your request and the codebase, then works a fixed gate sequence 0→5, stopping at the first gate that holds — no skipping, no escalating past a gate that already answered.
The output is a one-page verdict: the dial tier, a NEURAL / SYMBOLIC / HUMAN flowchart, the patterns explicitly NOT used (the list is the point), a v0 scope, and the top-3 failure modes mapped back to gates.
[assumed].v0, failure modes → gates. Under a page.Chains, routers, ReAct, orchestrator-worker… and the one choosing rule: can you draw the flowchart before runtime?
Open diagram → referenceThree build tiers — neurosymbolic, guarded judgment, deterministic pipeline — plus the two-question ambiguity test and the pyramid discipline.
Open diagram →# copy the skill into your Claude Code skills directory
cp -r skills/pick-gtm-agent-pattern ~/.claude/skills/
Then invoke it directly, or just describe the agent:
/pick-gtm-agent-pattern # or, in plain language — # "what pattern should this agent use?" # "make this workflow an agent" # "is this over-engineered?"