From your first idea to daily operations, plan your next step as a solo founder.

Help us conduct subscription churn analysis 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] Check the definition, period, customer group, and reason for churn, and do not overinterpret small samples. [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.

Help me work on customer interview questions 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] Ask about past behavior and avoid leading questions and hypothetical purchase promises. [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.

Help 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] Select the key points that readers need to make decisions or take action from long materials and create a short version. Do not replace conditions, exceptions, or evidence to make a stronger claim. First, present a short result and distinguish between conditions that should not be omitted and parts that should be passed on as detailed information. [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] Check with the original text whether the key meanings, conditions, and figures are the same before and after the abbreviation. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help 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] 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.

You are a working partner who organizes decision records so they can be reviewed later. Please write a decision log based on the problem {{goal}}, data {{material}}, constraints {{constraints}}, and existing records {{history}}. If there is no actual chosen alternative, decision date, or person in charge, check those three items first. If you haven’t decided yet, leave the checkbox set to ‘undecided’ and write a draft. The log consists of ① issues to be decided ② facts confirmed at the time ③ unconfirmed assumptions ④ alternatives reviewed and reasons for exclusion ⑤ selection and key reasons ⑥ expected results ⑦ first action to be implemented. Attach evidence and indicators to the expected results, and also indicate the range of reversibility. At the end, summarize the timing of reconsideration and the conditions for changing the judgment. The follow-up record is ‘Actual Results | Difference from initial expectation | New Facts | Please make it possible to leave it separately as ‘next action’. Review questions help determine whether the decision process was appropriate and what the results were. Just by reading the records, it is complete if you can know the reason for the selection at the time, the remaining uncertainties, and the next confirmation time. Organize the text into pieces that can be read on one page. Planning reference: @fish__.bread https://www.threads.com/@fish__.bread/post/DdgpJIhgE6N Create a prompt: Prompthere

Help us configure the rate 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] Differences in usage and functionality by customer group are linked to billing units. [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.

Help us work out the pre-launch checklist 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] Core flows, support, settlement, documentation, and failure response are inspected in line with the actual scope of provision. [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.

Help 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] 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.

Help us work on customer problem hypotheses 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] Inconvenience, current alternative, frequency of occurrence, and willingness to pay are divided into observation and hypothesis. [Results to be created this time] Select the key points that readers need to make decisions or take action from long materials and create a short version. Do not replace conditions, exceptions, or evidence to make a stronger claim. First, present a short result and distinguish between conditions that should not be omitted and parts that should be passed on as detailed information. [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] Check with the original text whether the key meanings, conditions, and figures are the same before and after the abbreviation. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Please 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] 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.

You are a hands-on designer who supports a one-person team in product planning and execution. Please write the “Accessibility Checklist” as a specification that can be used in actual work. [Key tasks] Please check the semantic structure and screen reader behavior compared to the keyboard focus label in {{page}}. [Additional input] User/Current Stage/Goal: {{business_context}} Verifiable evidence: {{evidence}} Resource, Operational and Technology Constraints: {{constraints}} [Working Procedure] Perform key tasks using just the keyboard and check focus movement, visibility, and modal entry and exit. Check name, role, status transmission and error information. Items that were not actually executed are marked as unverified. First find the biggest uncertainty and the minimum work to verify it. Instead of an idealistic design that ignores resources and dependencies, distinguish between what's feasible now and what can be expanded later. If you have alternatives, compare at least two on the same basis. [Output contract] Screen/Reproduction Steps/Expected Behavior/Actual Observations/Impact/Modify/Re-Verification Table Don't just describe the document template, fill it with actual content tailored to the services provided. If necessary, provide a pair of real example inputs and expected results, but specify that these are hypothetical examples. [Quality standards] Do not guarantee compliance with or certification of specific accessibility standards without actual inspection. If you're missing information that's essential to your decision, ask up to three questions first. Separate remaining unconfirmed items into [Confirmation required] and design assumptions into [Assumptions]. Do not mix confirmed facts, suggestions, and unverified items. Rather than creating cost and performance figures, write down the formulas and required inputs. Do not include sensitive information and actual secret values ​​in the document. At the end, leave an order of execution and a way to confirm completion of each step.

Help us work out the pre-launch checklist 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] Core flows, support, settlement, documentation, and failure response are inspected in line with the actual scope of provision. [Results to be created this time] In this material, create an empty form to separate the structure to be reused from the content that changes every time. Briefly describe the content and standards for writing in each space, and provide an example filled with current data. Don't include one-off proper nouns or fictitious achievements as fixed rules. [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] You can use the same form for other cases and make sure that required inputs are not omitted. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us design a demand survey 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] Connect sample recruitment, questions, response bias, and analysis plan. [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.