failure-postcardslisted

# Failure Postcards ## Overview This skill turns abstract risk into something a builder can feel. Instead of listing generic failure modes, it writes little artifacts from the future: support emails, bug reports, confused user notes, one-star reviews, postmortem fragments. The point is to make the failure legible fast. ## When to Use Use this when: - a design sounds good on paper but you do not trust it yet - the team is discussing risks too abstractly - you want a pre-mortem without corporate workshop energy - a key user flow needs pressure-testing from the user's side Do not use this as theatre. The goal is not to be dramatic. The goal is to expose real fragility. ## What to Produce Generate a small set of future artifacts such as: - support tickets - angry or disappointed emails - confused first-user messages - one-star reviews - short postmortem fragments Then explain: - what failure each artifact reveals - what assumption broke - what design change might prevent it ## Working Loop 1. Choose the fragile promise. Pick the feature, flow, or assumption that sounds good but may be hiding a break. 2. Jump forward in time. Imagine the moment after the failure has already happened. 3. Write the artifact from the human side. Let the support email, review, or postmortem fragment reveal what the builder failed to notice. 4. Decode the postcard. Explain the hidden assumption, why it broke, and what design move would reduce the chance of that future. ##