industry-truths

Create and update an industry assumptions document with time-horizoned truths.

1|Updated Jun 28, 2026
One-click install
npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill industry-truths-whmathews15
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: industry-truths
Source: https://github.com/whmathews15/DEX-Personal-Operating-System/tree/main/.agents/skills/industry-truths
Command: npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill industry-truths-whmathews15

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents strategic decisions from drifting onto outdated assumptions by capturing what is believed to be true at different time horizons.

Core Features & Use Cases

  • Time-Horizoned Truths: Organizes beliefs into Today, 6 Months, and 12 Months so strategy stays aligned with changing conditions.
  • Anti-Truth Tracking: Records beliefs that were discarded to make learning explicit and prevent repeated mistakes.
  • Review and Validation: Supports periodic updates that compare prior predictions with actual outcomes and refine future judgment.

Quick Start

Use the industry-truths skill to interview me about my domain and create or update my Industry_Truths.md file.

Frequently Asked Questions about industry-truths

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

FAQPage Schema
How do I document industry assumptions for strategic planning?

You document industry assumptions by creating an Industry_Truths.md file that captures beliefs across Today, 6 Months, and 12 Months horizons, ensuring your strategic planning stays grounded in evolving conditions rather than static views.

What is the best way to track invalidated strategic assumptions over time?

Tracking invalidated strategic assumptions is handled through anti-truth tracking, which records discarded beliefs explicitly to make learning visible and prevent repeating the same strategic mistakes in future planning cycles.

How do I validate my roadmap against changing industry conditions?

You validate your roadmap by performing periodic reviews against the industry assumptions document, comparing prior predictions with actual outcomes to refine future judgment and ensure roadmap alignment with current domain truths.

Can I use this for fast-moving domains like AI and enterprise software strategy?

Yes, this is designed for fast-moving domains such as AI, product management, and enterprise software, where capturing time-horizoned truths prevents strategic decisions from drifting onto outdated assumptions.

How do I start capturing my domain truths for roadmap review?

You start by prompting the skill to interview you about your domain, which structures your input into Today, 6-month, and 12-month truths, plus optional anti-truths, generating or updating your Industry_Truths.md file.