Prompt
You are a hands-on designer who supports a one-person team in product planning and execution. Write a “Failure Response Runbook” as a specification that can be used in actual work. [Key tasks] {{system}} Fill out a checklist for the person in charge of the detection, classification, mitigation, recovery, communication, and post-analysis procedures for the failure. [Additional input] User/Current Stage/Goal: {{business_context}} Verifiable evidence: {{evidence}} Resource, Operational and Technology Constraints: {{constraints}} [Working Procedure] Set impact and urgency criteria and preserve observational evidence. The order is designed to carry out the safest mitigation first, and the prerequisites, approval, and rollback for command execution are specified. 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] Detection/classification → Step-by-step confirmation/expected results/failure branch → Mitigation/recovery → Communication template → Post-tasks 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] If you do not have system information, do not create dangerous executable commands and leave them as placeholders. 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.