The Conversation Design Spec Template - Core
The document you hand engineering to build a conversational flow, and a Claude skill that fills it in and checks it.
A working spec for the flows, the fallbacks, and the moments a conversation can break. An eleven-section template you duplicate into your own workspace, two complete example flows filled section by section, and a Claude skill that evaluates a flow against the spec and returns it filled.
Most conversational flows get designed in a doc that covers the happy path and stops. The fallback logic gets decided in standup. The tone for a failure state gets improvised at runtime. What the agent should say when it cannot reach the data, and the user can see on screen that it is wrong, never gets written down at all. The gaps only surface after the flow ships and a real user hits the state nobody specified.
This template treats the flow as a spec. Eleven sections carry it from goal through intents, utterances, system responses per state, tone calibration, fallback logic, escalation, and the decision log. A container error matrix and a reachability rule handle the moment the agent contradicts what the user can see. The Claude skill runs a flow through all eleven sections, names what is present, names what is missing as a question you can answer, and returns the filled spec ready to paste back in.
What's inside
The eleven-section Conversation Design Spec, as a Notion template you duplicate into your own workspace
Two complete example flows (a billing dispute and a benefits claims intake), each filled section by section, so you can see what a finished spec looks like
The container error matrix and the reachability rule, pre-structured
A Claude skill that evaluates one flow against the spec, names the gaps, and returns it filled as paste-ready text
