Quality grade: defaultFeature priority, things to check before completionHelp us work on prioritizing features according to the goals and resources below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Compare customer impact, evidence, cost, and dependability and specify uncertain scores. [Results to be created this time] Extract conditions that can actually be confirmed from the data and create a checklist before submitting and sharing. For each item, please write down what to check, how to check, passing criteria, and what to do if not met. Leave unchecked items as unverified and reduce abstract checks that do not require any action. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each item is written with actual behavior and observable results. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.
Quality grade: defaultRetrospective on representative work, looking at the differences between alternativesPlease help me with the representative work retrospective according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Compare time use and actual results and choose what to delegate, stop, and keep. [Results to be created this time] If there are alternatives provided, compare them based on the same criteria. If not, suggest two possible approaches based on the current data. Distinguish between appropriate situations, pros and cons, required data, and what to give up for each approach. Rather than saying that one is unconditionally better, please write down the basis for your choice based on the input conditions. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that the comparison criteria and assumptions are applied equally to all alternatives. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultYour first sales conversation, what to check before completionHelp you work on your first sales conversation by aligning it with the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Design the conversation based on identifying the partner's problem, determining suitability, and next action. [Results to be created this time] Extract conditions that can actually be confirmed from the data and create a checklist before submitting and sharing. For each item, please write down what to check, how to check, passing criteria, and what to do if not met. Leave unchecked items as unverified and reduce abstract checks that do not require any action. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each item is written with actual behavior and observable results. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultMinimum product scope, from blank document to first draftHelp us work on the minimum product scope according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Separate functions to verify key hypotheses from functions to be performed later. [Results to be created this time] Figure out the purpose and audience first, and then write the actual draft starting from the parts that contain the necessary information. Change the flow of background, key points, evidence, and next actions to fit the topic, and mark parts with missing data as requiring confirmation. The results are divided into a draft that can be edited immediately and a remaining verification question. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure all the facts and figures in your draft match the input and allow the reader to know what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultPrototype evaluation criteria, summary to pass on to othersHelp us work on the prototype evaluation criteria according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Establish success criteria based on customer behavior and distinguish between favorable responses and actual usage. [Results to be created this time] Create a handover document focusing on the current status, what has already been decided, open questions, next actions, and data location. For the person in charge and the deadline, only write what is provided and leave the undecided ones as is. Leave the necessary context so that people who haven't read the original can take the first step. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure recipients know what to look for, where to look, and what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultFirst sales conversation, find gaps to review firstHelp you work on your first sales conversation by aligning it with the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Design the conversation based on identifying the partner's problem, determining suitability, and next action. [Results to be created this time] Read the provided draft and select the omissions, contradictions, and lack of evidence that prevent you from achieving your goal in order of greatest impact. Please include the original text location, problem, impact on readers, and minimum revisions. Don't treat simple differences in taste as errors, but be sure to identify what needs to be fixed before rewriting the entire thing. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that each problem you point out has textual support and that the amendments do not change the original meaning. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultImprove repeat purchases, see results and fix next versionHelp us improve repeat purchases in line with the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Find the reasons, cycles, and obstacles to repurchasing in the records. [Results to be created this time] Compare the initial goal and actual results and share good choices, stuck points, and lack of evidence. Instead of criticizing the judgment at the time based solely on the results, choose no more than two hypotheses to change. Please suggest indicators to maintain, change, and observe in the next attempt. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure you have concrete data to compare improvements to in the next attempt. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultExperience customer operation plan, find gaps to review firstHelp us work on the experiential customer operation plan according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Distinguish between participation conditions, scope of support, actions to be observed, and judgment after completion. [Results to be created this time] Read the provided draft and select the omissions, contradictions, and lack of evidence that prevent you from achieving your goal in order of greatest impact. Please include the original text location, problem, impact on readers, and minimum revisions. Don't treat simple differences in taste as errors, but be sure to identify what needs to be fixed before rewriting the entire thing. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that each problem you point out has textual support and that the amendments do not change the original meaning. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultScope of outsourcing request, items to check before completionPlease help us meet the scope of outsourcing requests according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Separate output, inspection standards, schedule, data, and scope of revision. [Results to be created this time] Extract conditions that can actually be confirmed from the data and create a checklist before submitting and sharing. For each item, please write down what to check, how to check, passing criteria, and what to do if not met. Leave unchecked items as unverified and reduce abstract checks that do not require any action. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each item is written with actual behavior and observable results. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultTimetable for recurring tasks, items to check before completionHelp with repetitive work schedule tasks according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Align essential operations, intensive work, and exception margins with actual available time. [Results to be created this time] Extract conditions that can actually be confirmed from the data and create a checklist before submitting and sharing. For each item, please write down what to check, how to check, passing criteria, and what to do if not met. Leave unchecked items as unverified and reduce abstract checks that do not require any action. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each item is written with actual behavior and observable results. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultInitial customer recruitment plan, looking at the differences between alternativesHelp us work on our initial customer recruitment plan based on the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Connects customer gathering places, contact points, suggestions, and response standards. [Results to be created this time] If there are alternatives provided, compare them based on the same criteria. If not, suggest two possible approaches based on the current data. Distinguish between appropriate situations, pros and cons, required data, and what to give up for each approach. Rather than saying that one is unconditionally better, please write down the basis for your choice based on the input conditions. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that the comparison criteria and assumptions are applied equally to all alternatives. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultMarket size assumption table, looking at the differences between alternativesHelp us work on the market size assumption table according to the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Reveals calculation formula, source, scope, and possibility of duplication and does not fill in unconfirmed numbers. [Results to be created this time] If there are alternatives provided, compare them based on the same criteria. If not, suggest two possible approaches based on the current data. Distinguish between appropriate situations, pros and cons, required data, and what to give up for each approach. Rather than saying that one is unconditionally better, please write down the basis for your choice based on the input conditions. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that the comparison criteria and assumptions are applied equally to all alternatives. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultCustomer support process, summary to pass on to someone elseHelp us work through our customer support processes according to the goals and resources below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Connect inquiry classification, priority, responsibility, response standards, and prevention of recurrence. [Results to be created this time] Create a handover document focusing on the current status, what has already been decided, open questions, next actions, and data location. For the person in charge and the deadline, only write what is provided and leave the undecided ones as is. Leave the necessary context so that people who haven't read the original can take the first step. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure recipients know what to look for, where to look, and what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultPrioritize growth experiments, find gaps to review firstHelp us prioritize our growth experiments according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Distinguish between hypothesis, expected impact, verification cost, and measurability. [Results to be created this time] Read the provided draft and select the omissions, contradictions, and lack of evidence that prevent you from achieving your goal in order of greatest impact. Please include the original text location, problem, impact on readers, and minimum revisions. Don't treat simple differences in taste as errors, but be sure to identify what needs to be fixed before rewriting the entire thing. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that each problem you point out has textual support and that the amendments do not change the original meaning. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultScope of outsourcing request, revisions reflecting feedbackPlease help us meet the scope of outsourcing requests according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Separate output, inspection standards, schedule, data, and scope of revision. [Results to be created this time] Compare the data with previous feedback, organize changes to be reflected, and write a revised version. For conflicting feedback, explain the options based on purpose and reader criteria. Briefly compare what was kept, what was changed, and the reason for the change, and do not add new facts. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure previously confirmed conditions are preserved and requested feedback is reflected. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultCriteria for stopping an idea, things to check before completionHelp me work on the idea stopping criteria according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Define the observation criteria and confirmation period required to determine continuation, modification, or discontinuation. [Results to be created this time] Extract conditions that can actually be confirmed from the data and create a checklist before submitting and sharing. For each item, please write down what to check, how to check, passing criteria, and what to do if not met. Leave unchecked items as unverified and reduce abstract checks that do not require any action. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each item is written with actual behavior and observable results. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultBarriers to industry entry, questions to ask before startingHelp us work on industry entry barriers according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Barriers in terms of technology, operations, distribution, and trust are distinguished, and legal requirements are left as items to be checked. [Results to be created this time] Distinguish between information that can be confirmed based on current data and information gaps that change the outcome. Write down the reasons for each question and the parts that vary depending on the answer, and suggest up to three questions to check first. Once you receive the answer, please update the agreed upon task summary. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Please check whether the question already has an answer in existing materials or is simply a question of preference. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultLooking at industry entry barriers and differences between alternativesHelp us work on industry entry barriers according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Barriers in terms of technology, operations, distribution, and trust are distinguished, and legal requirements are left as items to be checked. [Results to be created this time] If there are alternatives provided, compare them based on the same criteria. If not, suggest two possible approaches based on the current data. Distinguish between appropriate situations, pros and cons, required data, and what to give up for each approach. Rather than saying that one is unconditionally better, please write down the basis for your choice based on the input conditions. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that the comparison criteria and assumptions are applied equally to all alternatives. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultExperience customer operations plan, from blank document to first draftHelp us work on the experiential customer operation plan according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Distinguish between participation conditions, scope of support, actions to be observed, and judgment after completion. [Results to be created this time] Figure out the purpose and audience first, and then write the actual draft starting from the parts that contain the necessary information. Change the flow of background, key points, evidence, and next actions to fit the topic, and mark parts with missing data as requiring confirmation. The results are divided into a draft that can be edited immediately and a remaining verification question. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure all the facts and figures in your draft match the input and allow the reader to know what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultBusiness indicator dashboard, find gaps to review firstHelp us work on the business indicator dashboard according to the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Define calculation formula, source, cycle, responsibility, and action in case of abnormality for each indicator. [Results to be created this time] Read the provided draft and select the omissions, contradictions, and lack of evidence that prevent you from achieving your goal in order of greatest impact. Please include the original text location, problem, impact on readers, and minimum revisions. Don't treat simple differences in taste as errors, but be sure to identify what needs to be fixed before rewriting the entire thing. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that each problem you point out has textual support and that the amendments do not change the original meaning. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultBreak-even assumption, revised to reflect feedbackHelp me work out my break-even assumptions based on the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] It shows the calculation and sensitivity of fixed costs, contribution margin per case, and required sales volume. [Results to be created this time] Compare the data with previous feedback, organize changes to be reflected, and write a revised version. For conflicting feedback, explain the options based on purpose and reader criteria. Briefly compare what was kept, what was changed, and the reason for the change, and do not add new facts. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure previously confirmed conditions are preserved and requested feedback is reflected. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultCash flow check, summary to pass on to othersPlease help me with the cash flow check according to the goals and data below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Divide the timing of revenue recognition and actual deposits and withdrawals and find the timing of shortage. [Results to be created this time] Create a handover document focusing on the current status, what has already been decided, open questions, next actions, and data location. For the person in charge and the deadline, only write what is provided and leave the undecided ones as is. Leave the necessary context so that people who haven't read the original can take the first step. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure recipients know what to look for, where to look, and what to do next. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultOne-page business introduction, find gaps to review firstHelp me work on a business introduction according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Organize customer problems, solution methods, reasons for progress, and requests into one flow. [Results to be created this time] Read the provided draft and select the omissions, contradictions, and lack of evidence that prevent you from achieving your goal in order of greatest impact. Please include the original text location, problem, impact on readers, and minimum revisions. Don't treat simple differences in taste as errors, but be sure to identify what needs to be fixed before rewriting the entire thing. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that each problem you point out has textual support and that the amendments do not change the original meaning. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultImprove repeat purchases, find gaps to review firstHelp us improve repeat purchases in line with the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Find the reasons, cycles, and obstacles to repurchasing in the records. [Results to be created this time] Read the provided draft and select the omissions, contradictions, and lack of evidence that prevent you from achieving your goal in order of greatest impact. Please include the original text location, problem, impact on readers, and minimum revisions. Don't treat simple differences in taste as errors, but be sure to identify what needs to be fixed before rewriting the entire thing. [Working Principle] Distinguish between observed facts and business hypotheses to be tested. Do not fill in sales, demand, and costs arbitrarily, but leave actual basis and calculation conditions. Consider the resource constraints of your implementation. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that each problem you point out has textual support and that the amendments do not change the original meaning. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt