📦 NEW: Before You Build - Add product risk review skill

README.md

@@ -81,6 +81,7 @@ Skills work seamlessly with **Command Code**  providing consistent, high-quality
 ### Business Operations
 
 - **[Brand Guidelines](skills/brand-guidelines/)** - Applies brand colors and typography to artifacts for consistent visual identity and professional design standards.
+- **[Before You Build](skills/before-you-build/)** - Pressure-tests a product idea, landing page, MVP, or major feature before implementation by checking demand, positioning, monetization, retention, trust, distribution, and feature-adoption risk.
 - **[Competitive Ads Extractor](skills/competitive-ads-extractor/)** - Extracts and analyzes competitors' ads from ad libraries to understand messaging and creative approaches that resonate.
 - **[Domain Name Brainstormer](skills/domain-name-brainstormer/)** - Generates creative domain name ideas and checks availability across multiple TLDs including .com, .io, .dev, and .ai extensions.
 - **[Lead Research Assistant](skills/lead-research-assistant/)** - Identifies and qualifies high-quality leads by analyzing your product, searching for target companies, and providing actionable outreach strategies.

skills/before-you-build/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: before-you-build
+description: Pressure-test a product idea, landing page, MVP, or major feature before implementation. Use when the user wants to build something and needs to check demand, positioning, monetization, retention, trust, distribution, or feature-adoption risk first.
+---
+
+# Before You Build
+
+Use this skill before turning a product idea or feature request into implementation work.
+
+## When to Use
+
+- The user wants to build a new product, landing page, MVP, or app.
+- The user wants to add or change a major feature.
+- The user asks whether an idea is worth building.
+- The user is moving from product thinking into code.
+
+## Process
+
+1. Restate the idea in one plain sentence.
+2. Identify whether the idea is specific enough to judge.
+3. If it is too broad, ask who it is for, when they use it, what painful problem it solves, and what they use today.
+4. Find the single biggest risk: demand, positioning, monetization, retention, trust, distribution, or feature adoption.
+5. Separate weak signals from stronger evidence.
+6. Recommend the smallest validation step before implementation.
+
+## Output
+
+```md
+Verdict: [Build / Validate first / Narrow the scope / Stop]
+
+Biggest risk:
+- [The main reason this may fail.]
+
+Evidence gap:
+- [The missing proof that matters most.]
+
+Next validation step:
+- [One concrete action to run before building.]
+```
+
+## Guardrails
+
+- Do not recommend a tech stack.
+- Do not write code.
+- Do not turn a weak idea into a detailed build plan.
+- Be direct, concrete, and concise.