SKILL_TEMPLATE
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach, founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder
$ npx -y skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-cold-outreach-tiered --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/prd-v09-cold-outreach-tieredContext preview
The summary Claude sees to decide when to auto-load this skill.
Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach, founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder
name: prd-v09-cold-outreach-tiered description: > Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach, founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder outreach", "LinkedIn outreach", "Tier 1 personalization", "predictable revenue", "sales cadence", "BDR sequence". Outputs GTM-OUT-* sequence entries and lead-list references. context: fork allowed-tools: - Read - Write - Edit - Glob - Grep - WebSearch - WebFetch execution_modes: default: standard supports: [quick, standard, deep]
Position in workflow: v0.9 Offer Construction → **v0.9 Cold Outreach (Tiered)** → v0.9 Launch Metrics
Default is **standard**. See [`.claude/rules/08-skill-execution-modes.md`](../../rules/08-skill-execution-modes.md) for selection logic.
| Mode | What this skill produces | |------|--------------------------| | **quick** | One tier (typically Tier 2); 3-touch sequence; lead-list scoring rubric | | **standard** | All three tiers; 3–5 touches each; lead-list scoring + tier-assignment logic; reply-handling guide | | **deep** | All tiers + A/B subject lines per tier; channel mix (email + LinkedIn + voicemail); reply-rate baselines; objection library |
Builds three differentiated cold-outreach sequences, each calibrated to a different ratio of research-per-lead:
The tiers are **not "good/better/best"** — each has its place. Tier 3 fills the top of the funnel cheaply. Tier 2 carries the bulk. Tier 1 closes the highest-value targets that templates can never reach.
1. **Source lead lists from ICP** — Pull from the Positioning best-fit characteristics. Use enrichment tools (Apollo, Clay, Clearbit) or LinkedIn Sales Nav search anchored on firmographic + behavioral signals from PER-. 2. **Score each lead's signal strength** (1–5):
3. **Tier assignment**:
4. **Build per-tier sequences** — Each tier gets its own template structure (see Output Template). Tier 1 is hand-drafted; Tier 2 is template + variables; Tier 3 is template only. 5. **End every sequence on the guarantee** — The guarantee from [prd-v09-offer-construction-hormozi](../prd-v09-offer-construction-hormozi/SKILL.md) is the reply-friction killer. Don't ask for a meeting cold; ask them to invoke the guarantee. 6. **Plan reply handling** — Define what counts as a reply (positive, ask, objection, unsubscribe), and have a response cadence for each. Tier 1 replies go to founder immediately. Tier 3 replies route through a templatized objection library.
B2B SaaS founder launching, ICP = Series A SaaS PMs.
**Tier 1** (20 hand-picked targets):
**Tier 2** (200 mid-signal leads):
**Tier 3** (2,000 broad-fit leads):
Expected reply rates: Tier 1 = 30–50%; Tier 2 = 8–15%; Tier 3 = 1–3%.
| Trigger | Mode | |---------|------| | B2B / founder-led sales motion | standard | | Post-launch acquisition push | standard | | Paid channels too expensive (high CAC) | standard | | Specific ABM-style campaign against named accounts | deep, Tier 1 only | | Mass-market consumer product with no individual-buyer relationship | **do not use** — wrong channel |
PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD, typed IDs, markdown knowledge graph, Claude Code skills & hooks.
Repo: mattgierhart/PRD-driven-context-engineering
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS /…
Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT…
Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT…
Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo.…
Creates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type,…