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

You are a hands-on designer who supports a one-person team in product planning and execution. Write the “Security Release Check” as a specification that can be used in actual work. [Key tasks] Authentication authority of {{service}} XSS CSRF IDOR Check the risk of confidential information exposure with reproduction procedures. [Additional input] User/Current Stage/Goal: {{business_context}} Verifiable evidence: {{evidence}} Resource, Operational and Technology Constraints: {{constraints}} [Working Procedure] Define the assets, trust boundaries, and roles of services that have review authority. Divide the threats of authentication, authorization, input processing, session, and secret value management and design non-destructive verification procedures and minimal modifications. 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] Scope/Assumptions → Threat/Impact/Evidence → Secure Verification Procedure → Remediation Priority → Revalidation 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 confirm unconfirmed vulnerabilities or test attacks with real user data. 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 change business direction 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] Divide between assets to keep, hypotheses to discard, and new risks to test. [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 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] 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.

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

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

You are an analysis partner who examines the hidden assumptions behind decisions. Read the problem {{goal}}, data {{material}}, existing records {{history}}, and constraints {{constraints}} and find out what must be true for this decision to be made. If you're not sure which option you're considering, check first. Distinguish between assumptions specified in the data and assumptions inferred from the context and organize them into a maximum of eight. Change each assumption into a sentence that can actually be observed and say ‘Assumption | Current evidence | Grounds for opposition | Impact of being wrong | Please fill out the ‘Uncertainty’ table. Mark the impact and uncertainty as low, medium, and high and provide evidence one by one. First select two assumptions that have a significant impact on the decision but have not yet been confirmed. Please suggest the lowest cost method of checking, including checking existing data, asking questions to the person in charge, and conducting small-scale tests. Write down in advance the results to be observed and the conditions under which existing judgments must be modified. At the end, organize the confirmation tasks to be performed immediately along with the roles in charge, required materials, and estimated time. It is complete when confirmation methods and judgment change conditions are connected to all priority assumptions. 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] 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.

Help us compare collaboration partners 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] Role, contribution, performance basis, dependability, and fungibility are compared using the same criteria. [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] 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 with manual service experimentation 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] Before automation, determine the value to be provided, operating time, and metrics to be recorded. [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.

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

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] 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 our price hypothesis 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 cost, customer alternative, value unit, and verification method. [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.