Workflow
#sales-triggers
#timing
Sales Triggers Taxonomy
Workflows
Free, ungated
A strategic framework for identifying, scoring, and messaging B2B sales triggers. Timing is everything in outbound. Learn how to map a buyer's event directly to the downstream pain your product solves.
What's inside
| File | What it does |
|---|---|
.agents/skills/SKILL.md | Orchestrator and routing logic |
.agents/skills/trigger-identification-framework.md | Categorizing signals (Inbound, Bridgebound, Outbound, 3rd-Party) |
.agents/skills/trigger-to-message-mapper.md | Converting triggers into compelling premises |
.agents/skills/trigger-detection-automation.md | Infrastructure for listening to market signals |
.agents/skills/trigger-prioritization-scoring.md | "Time to Pain" (TTP) scoring model |
Prerequisites
- Intent data providers or LinkedIn Sales Navigator
- AI IDE (Claude Code, Cursor, Windsurf)
Installation
Cursor, Windsurf, or Generic AI IDE
- Clone the repo:
git clone https://github.com/forma-norden/sales-triggers-taxonomy - Copy the
.agents/skills/directory into your project's.agents/skills/folder.
Claude Code
- Clone the repo:
git clone https://github.com/forma-norden/sales-triggers-taxonomy - Copy the
.agents/skills/directory into your project's.claude/skills/folder.
Usage
Load the orchestrator in your IDE and state your goal. For example: How do I score a list of accounts that recently raised a Series B?
Running tests
Use the prompt tests in tests/ to validate expected behavior and edge cases before deployment.
tests/README.mdinsales-triggers-taxonomy- Load each skill and run the corresponding test prompt
- Compare output against the validation checklist before rollout
Who this is for
GTM engineers, RevOps leads, VP Sales, and founders at B2B companies with 50 to 500 employees who are building or consolidating their outbound infrastructure and want to reduce tool sprawl through better-engineered GTM systems.
Ecosystem connections
This repository is designed to work as part of the Forma Norden open-source GTM ecosystem.
Works with
| Repo | Relationship | When to use together |
|---|---|---|
gtm-plays-collection | Downstream | Once a trigger is identified and prioritized here, you select the matching "Play" from the plays collection to execute it. |
signal-based-list-building-workflow | Parallel | The list building workflow handles the physical scraping and data aggregation; this taxonomy defines WHAT data should be scraped. |
outbound-personalization-playbook | Downstream | The messaging frameworks provided here dictate the "Hook" that is written during the personalization workflow. |
Suggested skill chains
- Trigger Execution End-to-End:
trigger-identification-framework(define the event) >trigger-detection-automation(build the scrape) >signal-triggered-plays(execute the sequence) >copy-atl-executive-messaging(write the email).