talk-track-builder

name	talk-track-builder
description	Create persona- and stage-specific talk tracks for live conversations. Use when asked to draft, improve, or tailor call openers, discovery questions, demo flows, commercial talk tracks, or manager coaching prompts for AEs, SDRs, SEs, or managers. Route core positioning work to value-prop-and-positioning and objection handling systems to objection-library-builder.

Talk Track Builder

Build practical talk tracks that help sellers run clearer, more outcome-focused conversations.

Confirm Inputs First

• If a current revenue-enablement-context exists, use it first for ICP, persona language, stage labels, and proof standards.
• Confirm audience role and seniority (AE, SDR, SE, manager).
• Confirm persona and buying stage.
• Confirm use case or commercial motion.
• Confirm core value message and proof points.
• Confirm top objections or risk themes expected in the conversation.
• Confirm desired call outcome and next-step ask.
• If inputs are incomplete, ask for only the minimum missing items or proceed with labeled assumptions.

Read The Right Reference

• Read references/talk-track-framework.md before drafting tracks; use it for structure, branch logic, and stage-specific variants.

Default Workflow

1. Start with one call objective. Pick one outcome for the call and one concrete next step you want the buyer to agree to.
2. Pull the best source material. Use the value proposition, objection library, battlecard, and any recent release notes if they help.
3. Choose the track type. Pick discovery, demo, commercial, renewal, expansion, or manager coaching.
4. Outline the conversation flow. Use opener, context, questions, value bridge, proof, and close.
5. Write the actual lines. Keep the language short, conversational, and specific to the persona and stage.
6. Add proof inserts. Include short proof points the rep can say naturally without reading a script.
7. Add branch paths. Cover the likely turns: skepticism, pricing pressure, competitor comparisons, and multi-stakeholder pushback.
8. Add guardrails. Call out what not to say and where the rep should slow down or ask a question instead.
9. Add manager check points. Show what a manager should listen for if they are coaching against the track.
10. Route adjacent work: For message strategy, use value-prop-and-positioning. For objection playbooks, use objection-library-builder. For competitor counters, use battlecard-builder. For call coaching, use call-review-coach.

Output Contract

• Talk tracks versioned by role, persona, and stage.
• Discovery question set grouped by objective.
• Transition lines and checkpoint language.
• Proof snippets and when to deploy them.
• Branch-path response lines for common derailments.
• Manager inspection checklist for track adherence and effectiveness.
• Assumptions list when source inputs were incomplete.

What To Avoid

• Writing polished scripts that sound unnatural in live calls.
• Mixing discovery and demo goals into one unfocused conversation.
• Ignoring role/stage differences and shipping a one-size-fits-all track.
• Treating objection handling as one-line rebuttals without diagnostic questions.

Quality Bar

• Track sounds like natural speech rather than marketing copy.
• Questions create diagnostic insight, not generic rapport.
• Proof statements are specific and credible.
• Role and stage differences are explicit, not cosmetic.
• The next-step ask is concrete and testable.