before-you-build

1# Before You Build
2 
3Run a compact pre-mortem before implementation. The goal is not to block building; it is to identify the highest-risk assumption, the smallest validation step, and the build scope that should be delayed until evidence improves.
4 
5## When To Use
6 
7Use this skill when a user asks to build or ship:
8 
9- A new product, MVP, prototype, landing page, SaaS app, marketplace, content site, agent workflow, or internal tool
10- A major feature with unclear adoption, revenue, retention, trust, or distribution impact
11- A public launch asset where weak positioning could waste development or promotion effort
12 
13Skip this skill when the task is a narrow implementation fix, refactor, test repair, dependency update, or already-validated change with clear acceptance criteria.
14 
15## Risk Checklist
16 
17Review the idea across these risks:
18 
19- **Demand:** Is there evidence that a specific buyer or user urgently wants this?
20- **Positioning:** Can the target user understand what it is and why it matters in one sentence?
21- **Monetization:** Is there a credible path to payment, budget, or strategic value?
22- **Retention:** Is there a reason users would return after the first try?
23- **Trust:** Does the product require credibility, data access, integrations, or behavior change that users may resist?
24- **Distribution:** Is there a repeatable way to reach the target user?
25- **Feature adoption:** For feature work, will the feature change user behavior or just add surface area?
26…