Build · Create · Writing & Content

Build a frame-control response playbook

A frame-control playbook pairing each opposing frame with its book-correct Klaff counter-frame, a recognition trigger, and a ready response line.

You receive: A JSON object { pairings: [ { opposingFrame, counterFrame, triggerSignal, responseLine } x3 ] } covering each opposing-frame type exactly once.

Part of Pitch Investors

What's verified: STUD verifies the deliverable is a JSON playbook within a 100,000 character size bound, that your minimum-response-line-words setting sits inside a disclosed guard rail (1 to 60; a malformed setting falls back to the default of 8), and that the pairings array covers exactly the three opposing frames (power, time, analyst), each exactly once, each paired with its book-correct counter-frame (power busting, time constraining, intrigue), each carrying a recognition trigger of at least 5 words and a response line of at least your minimum word count (default 8), with no two pairings sharing the same response line. STUD does NOT verify that the lines fit your scenario, counterpart, or what you're pitching (those intake fields are operator context, not enforced criteria), that the triggers match how your counterpart actually behaves, or that a response line will win the frame collision in a live meeting: the word floors measure length, not persuasiveness.