Forked from@ashavega/A blunt review of my approach to a customer-support copilot
A blunt review of my approach to a customer-support copilot
I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.
Give me a short checklist for a customer-support copilot. I want something I can run before I call the work done.
Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Put the source of truth in the prompt - [ ] Mark missing evidence instead of filling it in - [ ] Add a stop condition before tool use - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.