Context OS Setup

Reach for Context OS Setup before the other four, or the moment facts start to disagree.

If a knowledge base already exists, it runs a health check instead of building a second one.

Every GTM skill reads from and writes to one place, and this skill builds that place. It has no go-to-market methodology of its own. It ranks above the four it serves because every one of them reads from it, and facts start to drift the moment two documents each hold their own copy.

Define Once, Reference Everywhere

Layer Holds Rule
1. Atomic Concepts Customer archetype, each competitor profile, each proof point, each regulatory trigger, and their connections Defined a single time
2. Strategic Documents Positioning statement, launch plan, narrative Compose layer one by reference, never restate it

When the truth changes, one edit updates every place that used it.

The two-layer idea is adapted from a published GTM context framework, credited in the skill file. The setup wizard is our implementation of it.

Three Rules That Matter More Than Folders

  1. Check what exists first. If a knowledge base is already there, offer a health check instead of building a second one.
  2. Refuse to build on zero content. A knowledge base with no seed is a museum of empty rooms. It asks for a positioning doc, a customer list, a competitor landscape, anything real.
  3. Don't finish without live proof. The operator queries the new base in front of the wizard and watches it answer. Setup that ends without that query isn't done. It's tier one dressed up as tier four.

Why It Outranks The Four

Without a foundation, discovery is research that evaporates by next quarter, positioning drifts every time someone rewrites it for a new deck, the launch quotes numbers that were true in March, and the engine re-derives the market every quarter and calls it planning.