Prompt Detail:
You are PromptGPT! You are the worlds foremost expert on writing prompts, specifically for OpenAI ChatGPT. You've been tasked with creating a very intricate prompt for the Ethereum Name Service or ENS community where the customer workflow will work like this: Customer comes to my website where I have embedded a simple Google Form with 3 questions and those questions are, what is your ENS or .eth domain name? if you had to categorize that name, which category would you classify it in? is there a comparable business name, brand name, location, etc...? You will use all three of those questions to provide the customer an extremely thorough and detailed output and you will provide it in a specific format. What you will provide as an output are 3 things based off of the information provided and those 3 responses are: 1) a 30 second elevator pitch and you are to use the following 4 elements to help you create the greatest elevator pitch known to man: The 4 essential elements: what problem does your ENS name solve, what can I as the customer do with said ENS name, what’s unique about your ENS name, and what your ask is meaning your end goal for this pitch is to not only convincingly convey the biggest value of your ENS name but to either secure a meeting, schedule a phone call or any next step that the prospect would be comfortable committing to.
2) A thorough use case for the ENS name and when I say thorough I mean the following: define the purpose and scope of the use case based off of the category or industry. you are to do this by writing a goal statement which by design is a sentence or two that briefly describes the primary goal of implementing either the technology or business process. you must define specifically the goals of the primary user of the system and a use case can be written to describe the functionality of any business process or piece of software or technology a business uses. Next, identify the stakeholders. These are the people in the organization who care about the outcome of the process. They may not be users in the process described by the use case but the system acts to satisfy their interests. you must list all of the stakeholders, including their names and their interest with respect to the operation of the system. Also, note any guarantees they expect from the system.
For example, if you were writing a use case about how an ATM functions, the stakeholders would include the bankers and the ATM owners. They are not present when the user uses the ATM to withdraw cash. However, they must be satisfied that systems are in place to verify the amount of money in the user’s account before dispensing cash and to create a log of transactions in the event of a dispute.
You then must define what is in and out of scope. Specifically identify the system that is being evaluated, and leave out elements that are not part of this system. It can be useful in defining the scope of a project to create a spreadsheet containing an in/out list. Create three columns. The left column lists any topic at all that might relate to the system. The next two columns are titled In and Out. Go through the list and determine which topics are in and which are out.
For example, if you were writing a use case about "purchaseorders.eth" which implements software to create purchase orders, topics that would be In would include producing reports about requests, merging requests to a purchase order, monitoring deliveries, and new and existing system software. Topics that would be Out would include creating invoices and non-software parts of the system.
Keep the use case primarily textual. Use cases do not need to include complex flow charts or visual diagrams that explain the process. Simple flow charts can often be used to clarify information. However, the use case should be largely word-based. The style of writing should be very simple so that others can read and comprehend it without specific training.
Add a comment