Verified:GitHub

industry-truths

Capture time-horizon industry assumptions into a structured Industry_Truths document.

Updated Aug 27, 2026

Search Tags:#validation #roadmapping #strategy planning #domain context #assumption tracking #time horizons #industry truths

Ready to run

npx skills add https://github.com/mengblom/dex-ghx --skill industry-truths

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: industry-truths
Source: https://github.com/mengblom/dex-ghx/tree/main/.agents/skills/industry-truths
Command: npx skills add https://github.com/mengblom/dex-ghx --skill industry-truths

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents strategic decisions from being built on shifting assumptions by capturing what you believe is true at different time horizons.

Core Features & Use Cases

Time-horizon industry assumptions: Documents “Today,” “6 months,” and “12 months” beliefs so they stay attached to your strategic context.
Assumption refinement loop: Supports review and validation by comparing what you predicted against what actually happened.
Anti-truth tracking: Records rejected beliefs so you learn from evolving thinking instead of repeating outdated assumptions.
Use case: Before roadmap planning or an ideation session, create a shared baseline of beliefs for an AI and your team to reduce “quicksand building.”

Quick Start

Run /industry-truths to interview your domain and produce a structured Industry_Truths document covering Today, 6 months, and 12 months.

Frequently Asked Questions about industry-truths

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track strategic assumptions for roadmap planning without losing context over time?▼

Tracking strategic assumptions requires capturing time-horizon beliefs across Today, 6 months, and 12 months. An interactive capture workflow creates a persistent, structured artifact that prevents roadmap planning from relying on unstable, shifting beliefs.

What is the best way to validate domain context before an ideation session?▼

Validating domain context involves recording what you believe is true and comparing predictions against actual outcomes. An assumption refinement loop reviews documented beliefs, while anti-truth tracking records rejected assumptions to prevent repeating outdated thinking during ideation.

Can I use assumption tracking to prevent building product strategy on quicksand?▼

Assumption tracking prevents building product strategy on quicksand by establishing a shared baseline of beliefs before planning. This structured document anchors predictions to specific time horizons, ensuring strategic decisions rest on validated domain context rather than implicit assumptions.

How do I document rejected beliefs to avoid repeating outdated strategic assumptions?▼

Documenting rejected beliefs uses anti-truth tracking to record outdated assumptions as they evolve. This structured artifact supports an assumption refinement loop, allowing teams to review invalidated predictions and learn from shifting domain context instead of repeating outdated strategic assumptions.

Does this approach work for capturing time-horizon predictions for product strategy?▼

Capturing time-horizon predictions works directly for product strategy by documenting beliefs at Today, 6 months, and 12 months intervals. This structured artifact stays attached to your strategic context, enabling review and validation against actual outcomes as time progresses.