How Beam Next Works

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 PROJECT**:
- 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 → PROJECT
│           └─ NO → Just do it (no structure needed)

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

The public **beam-next-skills** registry lists on the order of **140+** skills (integrations, learning, productivity). Your workspace loads **system** skills from `00-system/skills/` and **your** skills from `01-skills/` — you can add more anytime.

Ask: "Does the PROJECT vs SKILL distinction make sense?"

Wait for response. If unclear, clarify. If clear, continue.

Part 3: Memory (1 min)

Display:

----------------------------------------------------
🧠 PART 3: Memory
----------------------------------------------------

Beam Next remembers you across sessions.

**Key file**: 02-memory/goals.md

Contains:
- Your role & expertise
- Short-term goals (3 months)
- Long-term vision (1-3 years)
- Work style & preferences

**How it works**:
- Set during onboarding (quick-start)
- Loaded every session automatically
- I always know your context

**Why this matters**:
Instead of:
  "I'm a PM at a B2B SaaS company projecting a new feature..."

You just say:
  "Help me plan the Q2 roadmap"

And I already know your role, company type, goals, and style.

**Other memory files**:
- core-learnings.md → Insights from past work
- session-reports/ → History of what we've built
- user-config.yaml → Preferences & settings

Ask: "Have you completed the quick-start onboarding?"

If NO → "I recommend completing onboarding to set up your goals and workspace" If YES → "Great! That's why I understand your context."

Part 4: Workspace (1 min)

Display:

----------------------------------------------------
[DIR] PART 4: Workspace
----------------------------------------------------

Your persistent file storage.

**Location**: 04-workspace/

This is YOUR space for:
- Documents you want me to access
- Templates & frameworks
- Project archives
- Any persistent content

**Structure**:
04-workspace/
├── input/              # Drop files here for analysis
├── templates/          # Reusable frameworks
├── projects/           # Organized work
└── workspace-map.md    # Navigation guide for AI

**workspace-map.md**:
Documents your folder structure so I can navigate efficiently.

**Example**:
```yaml
04-workspace/
├── brand-strategy/
│   ├── canvas-template.md
│   └── positioning-framework.md
├── client-projects/
│   └── acme-corp/
└── research/
    └── competitor-intel/

When you say "use my brand canvas template", I know exactly where to find it.

Setup: Workspace is configured during quick-start onboarding.

---

### Part 5: Sessions (1 min)

**Display**:

[SYNC] PART 5: Sessions

Work persists automatically. No saving required.

How it works:

1. Start session: Type 'Hi' → Shows menu with current work & options

2. Do work: Build, execute skills, chat → Progress auto-saves continuously

3. Close session: Type 'close session' → Creates session report → Captures learnings → Everything ready for next time

4. Next session: Type 'Hi' → Resume exactly where you left off → Or start new work

Context continuity:

• Active BUILDs → Always visible in menu
• Memory → Loaded automatically
• Workspace → Always accessible
• State → Tracked in user-config.yaml

Example flow: Monday: "Build competitor research" → Plan phase → Close Tuesday: "Hi" → Menu shows "Continue Competitor Research (40% done)" → Resume Wednesday: Complete → Deliverables in 04-outputs/ → Archive

**Display**:

[OK] TOUR COMPLETE!

You now understand: [OK] BUILDs → Finite work with deliverables [OK] SKILLs → Repeatable workflows [OK] Memory → Your persistent context (goals.md) [OK] Workspace → Your file storage (04-workspace/) [OK] Sessions → Work persists automatically

Quick Reference:

• New work with deliverables → "build [name]"
• Repeating task → "create skill [name]" or use existing
• See options → "list skills"
• Start session → "Hi"
• End session → "close session"

Recommended next steps:

1. Start your first PROJECT: "build [what you want to create]"
2. Explore skills: "list skills"

Type 'Hi' to see the menu, or tell me what you want to work on.

---

## Post-Completion Actions

**Update Config**:
```python
from beam_next.state_writer import update_yaml_path

config_path = "00-system/core/beam_next/templates/user-config.yaml"
update_yaml_path(config_path, "learning_tracker.completed.how_beam_next_works", True)

Return to menu or user request.

Implementation Notes

Tone: Conversational, explain through examples, use visuals (trees, flows) Pacing: Pause for questions between parts Depth: Overview level, not deep implementation details Goal: User understands the mental model of Beam Next