how-nexus-works

How Nexus Works

Quick 7-minute tour of Nexus concepts and workflows.

Purpose

Help users understand the core architecture of Nexus: what BUILDs and SKILLs are, how memory and workspace work, and how to use the system effectively.

Time Estimate: 7 minutes

---

Workflow

Part 1: BUILDs (2 min)

Display:

----------------------------------------------------
🏗️  PART 1: BUILDs
----------------------------------------------------

A BUILD is finite work with a clear beginning, middle, and end.

**Examples**:
[OK] Research competitor landscape → Report
[OK] Design brand strategy → Framework
[OK] Create onboarding docs → Documentation
[OK] Plan marketing campaign → Strategy

**NOT a BUILD**:
[FAIL] Weekly status reports (repeating task)
[FAIL] Daily standup notes (ongoing workflow)
[FAIL] Code formatting (repeating automation)

**Rule**: If it ENDS, it's a BUILD. If it REPEATS, it's a SKILL.

**BUILD Structure**:
02-builds/ID-name/
├── 01-planning/        # Think before you execute
├── 02-resources/       # Research & materials
├── 03-work-in-progress/# Drafts & iterations
└── 04-outputs/         # Final deliverables

**Lifecycle**:
1. 'plan build' → Define what you want
2. Planning phase → Answer discovery questions
3. 'execute build' → Work through phases
4. Completion → Deliverables in 04-outputs/
5. Archive → Moves to 02-builds/complete/

**Example**: "Research Competitors"

When you say "build competitor research", Nexus:
1. Asks: Who are your competitors? What do you want to know?
2. Creates: Planning document with research questions
3. Executes: Searches, analyzes, compiles findings
4. Delivers: competitor-analysis.md in 04-outputs/
5. Archives: Project moves to 02-builds/complete/ when done

Ask: "Do you have any questions about BUILDs so far?"

Wait for response. If user asks questions, answer them. If not, continue.

---

Part 2: SKILLs (2 min)

Display:

----------------------------------------------------
⚡ PART 2: SKILLs
----------------------------------------------------

A SKILL is a repeatable workflow you can execute anytime.

**Examples**:
[OK] 'close session' → Save progress, create report
[OK] 'list skills' → Show available workflows
[OK] 'mental models' → Apply thinking frameworks
[OK] Integration skills (if you add Slack, Airtable, etc.)

**When to create a SKILL**:
- You'll do this task more than once
- It's a standardized workflow
- Others might reuse it

**When to create a BUILD**:
- It's one-off work with deliverables
- You want structured planning & outputs
- It has a clear completion point

**Decision Tree**:
┌─ Does it repeat?
│  ├─ YES → SKILL
│  └─ NO ┐
│        └─ Does it have deliverables?
│           ├─ YES → BUILD
│           └─ NO → Just do it (no structure needed)

**How to load skills**:
- Type the skill name: 'close session', 'mental models'
- Or browse: 'list skills'

Nexus has 50+ built-in skills, and you can create your own.