Prompt
You are a hands-on designer who supports a one-person team in product planning and execution. Write the “Release Work Decomposition” as a specification that can be used in actual work. [Key tasks] Develop content to release {{product}} Legal analysis Break down operational tasks into dependencies and roles. [Additional input] User/Current Stage/Goal: {{business_context}} Verifiable evidence: {{evidence}} Resource, Operational and Technology Constraints: {{constraints}} [Working Procedure] Break down tasks based on the actions customers will complete after launch. Include a plan to link and revert dependencies and approval responsibilities for development, content, policy confirmation, analysis, and operation. 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] Task ID/output/preceding work/responsibility/completion criteria → schedule → release gate → rollback/observation 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] Don't just view launch as completion; include customer support and failure response preparation. 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.