gtm-outreach
/gtm-outreach — Sales Outreach & Pipeline Generation
Build multi-channel outreach sequences, prospecting strategy, personalization frameworks, and reply handling playbooks. Focused on the outbound motion — distinct from content marketing.
When to Use
- User says "outreach", "cold email", "sequences", "prospecting", "SDR playbook"
- Building outbound pipeline generation
- Designing multi-channel sequences (email + LinkedIn + phone + video)
- Need prospecting criteria or reply handling playbooks
Before Starting
Check for existing context:
- Read
projects/<project>/gtm-context.md— master context - Read
projects/<project>/icp-personas.md— buyer language and personas (critical for personalization) - Read
projects/<project>/competitive-intel.md— competitive messaging gaps - Read
projects/<project>/positioning.md— messaging pillars
More from elliottrjacobs/bench-skills
product-prd
Write product requirements documents from feature ideas or brainstorm output. Use when the user says "write a PRD", "product requirements", "feature spec", or needs to formalize a product concept into a structured document.
17product-tech-spec
Write technical specifications bridging product requirements and implementation. Use when the user says "tech spec", "technical spec", "architecture doc", "system design", or after writing a PRD and before planning implementation.
11product-naming
Expert naming process for products, companies, and features based on David Placek's methodology. Use when the user says "name this", "brainstorm names", "naming process", or needs to find a name for a product, feature, company, or project.
10knowledge-compound
Document solutions, decisions, and learnings into a searchable knowledge base. Use when the user says "document this", "compound this", "save this solution", "capture this", or after completing significant work that uncovered reusable knowledge.
8security-audit
Deep security audit of codebase with parallel domain-focused agents. Use when the user says "security audit", "check for vulnerabilities", "security review", or before a launch/deployment. More thorough than the security reviewer in /engineer-review.
8engineer-review
Comprehensive multi-agent code review with parallel specialist reviewers. Use when the user says "review this", "code review", "review my PR", provides a PR number or branch, or after completing a /engineer-work cycle.
8