Prd V08 Marketing Ops Handoff

What it does

When your agent uses it

• Requests to set up lead lifecycle
• Define MQL/SQL criteria
• Build handoff process
• User asks whats an MQL?

Example prompts

• “s an MQL?”
• “marketing to sales handoff”
• “lead lifecycle”
• “/prd-v08-marketing-ops-handoff”

Requirements

• Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Pick the lifecycle shape — Match the product
2. 2Define entry criteria per stage — What event/behavior moves a lead into this stage? Examples
3. 3Define exit criteria per stage — Two paths out: progress (to next stage) and disqualify (back to nurture or out). Disqualification rules…
4. 4Map ownership — Who owns the lead at each stage
5. 5Define handoff payload — When a lead moves between owners, what context goes with them? At minimum
6. 6Set SLAs per stage — How fast must the new owner respond after handoff? MQL → BDR typically <1 business hour for high-signal, <1 business…
7. 7Plan rejection routing — When SQL → AE handoff is rejected ("not a fit"), where does the lead go? Back to nurture, disqualified, requeued?…

What it can do on your machine

Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Glob
  • Grep

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd V08 Marketing Ops Handoff loads about 2.7k tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 1,069 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~118

When it runs · the whole SKILL.md, loaded when a task matches

~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 1,069 words, ~2,698 tokens.

name

prd-v08-marketing-ops-handoff

description

Define lifecycle stages and marketing → sales / CSM handoff rules for leads captured by GTM channels during PRD v0.8 Deployment & Ops. Triggers on requests to set up lead lifecycle, define MQL/SQL criteria, build handoff process, or when user asks "what's an MQL?", "marketing to sales handoff", "lead lifecycle", "lead routing", "RevOps", "MOPS", "marketing operations". Outputs BR-MOPS-* lifecycle rules and GTM-MOPS-* handoff flow entries.

allowed-tools

Read, Write, Edit, Glob, Grep

context

fork

execution_modes.default

standard

execution_modes.supports

quick, standard, deep

BR-MOPS-XXX: Lifecycle Stage — [Stage name]
Type: Lifecycle-Stage
Order: [#]
Status: Active

Stage: [Anonymous | Signup | Activated | MQL | SQL | Opportunity | Customer | Expansion]

Entry criteria:
  - [Criterion 1 — e.g., "Filled out demo request form"]
  - [Criterion 2 — e.g., "Reached usage threshold X"]

Exit criteria (progression):
  - To [next stage]: [Criterion]

Exit criteria (disqualification):
  - [Criterion that routes back to earlier stage or out]

Owner: [Marketing automation | BDR/SDR | AE | CS | Founder]

SLA:
  Response time after entering this stage: [duration]
  Escalation: [What happens if SLA missed]

Linked IDs: PER-XXX (fit signals), GTM-YYY (source channels), BR-PRICING-ZZZ (tier threshold), KPI-AAA (conversion rate)

GTM-MOPS-XXX: Handoff — [Stage A] → [Stage B]
Type: Handoff
Status: Active

From: [Stage A] (owner: ...)
To: [Stage B] (owner: ...)

Trigger: [Specific event — e.g., "BDR marks lead as Qualified in CRM"]

Payload (what context transfers):
  - Source: [GTM-* channel]
  - Touchpoint history: [What they engaged with]
  - Best-fit signals: [Firmographic + behavioral match]
  - Disqualifiers: [Anything that ruled out earlier stages]
  - Open questions: [What new owner should clarify]

Rejection rule:
  Condition: [When does the new owner reject this handoff?]
  Routing: [Where does the rejected lead go? Nurture / disqualified / requeue]
  Re-engagement: [Conditions under which this lead can return]

SLA: [Response time required from new owner]

Linked IDs: BR-MOPS-AAA (Stage A rule), BR-MOPS-BBB (Stage B rule)

© mattgierhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/prd-v08-marketing-ops-handoff of mattgierhart/PRD-driven-context-engineering.

Open the folder on GitHubat commit 30ed1b0