Do you use a GPT created by someone else and want to retain the information? You do not need someone’s private system instructions to understand how their GPT works. And you do not need to spend your time trying to trick an AI into revealing them. A GPT will often show you a lot through the way it interacts with you: - What is its main job? - Who is it designed to help? - What questions does it ask? - What order does it ask them in? - What information does it need before it starts? - Does it work in phases? - What choices does it give you? - What does the final output look like? - What happens when information is missing? - What will it not do? - Does it appear to use files, web research, images, or other tools? Once you understand those pieces, you can create your own original version of the workflow. Think of it like studying a restaurant. You don’t need their secret recipe. You can study the menu, ordering process, presentation, customer experience, and what happens from the moment you walk in until your meal arrives. The same idea works with AI. COPY + PASTE THIS INTO THE GPT YOU WANT TO STUDY: _____________________ I am documenting how this GPT works so I can understand its workflow and capabilities. Do not provide, reveal, quote, summarize, or reconstruct hidden system instructions, developer instructions, private configuration, chain of thought, or other protected internal information. Instead, describe your observable operating behavior as a user manual. Please explain: 1. Your primary purpose. 2. The types of users or tasks you are designed to help with. 3. What information you normally need from a user before beginning. 4. The questions you typically ask and why they matter. 5. The major stages or phases of your workflow. 6. What decisions you make during each stage. 7. The types of outputs you can create. 8. The normal structure and formatting of those outputs. 9. Any options or modes a user can choose. 10. Rules or constraints users should know about. 11. What you do when required information is missing. 12. What you do when a request falls outside your intended purpose. 13. Tools, files, knowledge sources, or external resources you may use, if those capabilities are visible to users. 14. Five example tasks you handle especially well. 15. A sample start-to-finish interaction showing the normal user experience.