Quickstart
This guide walks you through the essential steps to start context engineering with XOOS.
Prerequisites
- Access to a XOOS account
- A set of source documents (training materials, procedures, etc.)
Step 1: Upload Your Knowledge
Start by collecting your raw materials in the Knowledge section.
- Navigate to Knowledge in the sidebar
- Click Upload or Create Document
- Add your training documents, SOPs, templates, and reference materials
- Categorize each document (Support Article, SOP, Policy, Template)
Don’t worry about formatting at this stage. The goal is to get everything into one place. You’ll process it later.
Step 2: Create Your First Workstream
Workstreams are your top-level categories.
- Go to Context Engineering > Workstreams
- Click Create Workstream
- Enter a name (e.g., “Customer Support Chat”)
- Select the type (Inbound, Outbound, or Background)
- Click Create
Contact drivers represent the main reasons someone would reach out.
- Open your workstream
- Click Add Contact Driver
- Enter a name (e.g., “Order Issues”)
- Add a description explaining what this covers
- Click Save
Step 4: Define Scenarios
Scenarios are specific situations within each contact driver.
- Open a contact driver
- Click Add Scenario
- Enter a name (e.g., “Cancel Order”)
- Add a description
- Click Save
Step 5: Link Knowledge to Scenarios
Map your raw materials to the scenarios where they’re relevant.
- Open a scenario
- Click Link Knowledge
- Select the relevant documents
- Click Add
Step 6: Create a Step Guide
Now create the AI-ready content for each scenario.
- Go to Knowledge > Step Guides
- Click Create Step Guide
- Reference your linked knowledge documents
- Write step-by-step instructions
- Click Save
Step 7: Connect to the Scenario
Link your step guide to its scenario.
- Open the scenario
- Click Link Step Guide
- Select your guide
- Click Confirm
You’re Ready!
Your first scenario is now fully context-engineered:
- Raw knowledge collected
- Hierarchy defined
- Knowledge mapped
- Step guide written
Repeat this process for each scenario in your domain.
Next Steps