Find what is actually broken in the workflow.
Cuts past the symptom to the real workflow that is costing you, whether that is lead scoring, enrichment, or reps buried in prep, and names the real problem.
In plain English: “What exactly is the problem to solve?”
Inside: How to find the real problem, the test that confirms it, and a worked example.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
Everything the skill does, in full.
Finds the one workflow worth fixing first and writes the problem as a workflow instead of a headcount. The reflex when a GTM team is stretched is to add a role. That names a hire, not a problem. This move points you at the work.
- 11. List the crossings, not the org chart. Walk the revenue lifecycle end to end and write down every place work passes between functions or is shared by more than one. Those are your workflows.
- Find the leaks two fast ways. Follow the spreadsheets: every recurring manual export, copy-paste, or cleanup job is a workflow with no system. Follow the "whoever has five minutes" work: anything that falls to whoever is free is unowned by definition.
- Size each in cost, not annoyance. Hours per week, pipeline leaked, or churn. Rank them.
- Pick the single most expensive one. That is the only workflow worth a project this quarter.
- Write the problem as a workflow sentence. "Inbound leaks between marketing and sales" is a workflow. "We need a GTM Engineer" is a headcount. If your sentence names a person, rewrite it until it names the work.
- Naming a role instead of a problem. A job req is not a fix.
- Ranking by what is loudest instead of what is most expensive.
- Trying to fix the whole funnel at once and learning nothing.
[the one workflow you picked, and what it costs you per week today]
Hand the workflow to Stack the Tech. The Sales Operator. Receipts only.
Where an operator takes this next.
Naming the workflow is step one. Here is where an operator takes it once the pick is made.
Name the workflow once, and the system keeps pointing you at the next one.
Wire a scheduled Claude task to pull weekly time-in-stage from Salesforce and flag which handoff is slipping, so the ranking updates itself instead of a quarterly guess.
Have Slack ping the workflow owner the moment a lead sits unrouted past your SLA, instead of finding it in next month's audit.
Hand the ranked workflow to a scheduled task that drafts the signal list automatically, so Solve and Stack the Tech run back to back without re-typing the brief.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.