Chat Assistant App Spec
By Jamie · Published · Updated
Scopes a chat assistant app before it is built: what users hire it for, the tools it needs, the guardrails and how success is measured.
Prompt template
## Chat Assistant App Spec Scope a chat-based assistant product. - Product idea: [textarea: Who it serves and the problem it addresses] - Main user jobs: [textarea: The three to five things users will ask it to do] - Data and tools it can reach: [textarea: Databases or APIs or documents it may use] - Risk level: [dropdown: Low stakes, Business sensitive, Regulated or safety related] - Handoff to a person: [toggle: Yes, No] - Launch audience: [dropdown: Internal staff, Existing customers, Public] Start with the user jobs and for each one write a sample request, the ideal reply and what counts as failure. Decide which jobs need a tool call and define each tool by name, inputs, outputs and whether it only reads or can change things. Any tool that changes data needs a confirmation step. Write guardrails as concrete rules: topics it declines, facts it must cite from a source, data it never repeats back, and the exact wording for I do not know. If handoff is on, define the triggers and what context passes to the person. Set success metrics with a number and a way to measure each, such as task completion rate, wrong-answer rate from sampled chats and handoff rate. Propose a test set of twenty realistic conversations including five hostile ones. End with launch stages and what would stop the rollout.