begin-workspace

Read Onboarding State

At startup, read ~/Tandem/.onboarding-state.md to recover session context:

• language — use for all output throughout this phase
• role — for role-aware connector pre-check (begin-connectors) or workspace creation (begin-workspace)
• use_cases — for priority use cases context
• tools_selected — for which connectors to set up (begin-connectors only)

---

Step 6: Workspace Creation

Create the full workspace structure at ~/Tandem/.

6a. Create root folder and files

Create ~/Tandem/ directory.

Root files

Create ~/Tandem/CLAUDE.md — use content from references/workspace-root-files.md (section: "CLAUDE.md template") Create ~/Tandem/MEMORY.md — use content from references/workspace-root-files.md (section: "MEMORY.md template")

Create ~/Tandem/memory/ subdirectories and initial files — see references/workspace-root-files.md (section: "Memory sub-files")

mkdir -p ~/Tandem/memory/people
mkdir -p ~/Tandem/memory/projects
mkdir -p ~/Tandem/memory/decisions
mkdir -p ~/Tandem/memory/sessions

6b. Create ALL standard subfolders

Create ALL standard subfolders regardless of what the user selected in use cases. The user's selections are stored in memory/preferences.md as "priority use cases" — they don't control which folders get created. This ensures the workspace is complete from day one, even for use cases the user discovers later.

email/ subfolder

Create ~/Tandem/email/CLAUDE.md and ~/Tandem/email/MEMORY.md — see references/workspace-email.md

documents/ subfolder

Create ~/Tandem/documents/CLAUDE.md and ~/Tandem/documents/MEMORY.md — see references/workspace-documents.md

research/ subfolder

Create ~/Tandem/research/CLAUDE.md and ~/Tandem/research/MEMORY.md — see references/workspace-research.md

tasks/ subfolder

Create ~/Tandem/tasks/CLAUDE.md, ~/Tandem/tasks/MEMORY.md, ~/Tandem/tasks/kanban.md, ~/Tandem/tasks/archive.md — see references/workspace-tasks.md

projects/ subfolder

Create ~/Tandem/projects/CLAUDE.md and ~/Tandem/projects/MEMORY.md — see references/workspace-projects.md

6b-extra. Create examples/ folders

For each workspace subfolder created above, also create an examples/ directory with a README explaining what to put there. This lets users drop in style examples so Claude can learn their preferences.

For ALL subfolders (email/, documents/, research/, tasks/, projects/):

Create ~/Tandem/<folder>/examples/README.md (in user's language):

# Examples

Place example files here so your assistant can learn your style and preferences.

Examples of what to put here:
- [folder-specific examples — see below]

Your assistant will check this folder before creating new content, so it can match your
preferred style, formatting, and tone.

Folder-specific guidance (include in the README):

• email/examples/: "Example email replies you've written, email templates, signature blocks"
• documents/examples/: "Example reports, budgets, presentations — anything showing your preferred formatting and style"
• research/examples/: "Example research outputs you liked, preferred report formats"
• tasks/examples/: "Example daily plans, task board layouts, weekly review formats"
• projects/examples/: "Example project briefs, status reports, project folder structures"

6b-subdirs. Create document type subdirectories

ALWAYS create these subdirectories inside ~/Tandem/documents/:

~/Tandem/documents/excels/
~/Tandem/documents/presentations/
~/Tandem/documents/reports/

These match the file placement rules in documents/CLAUDE.md. Creating them upfront ensures the assistant saves documents to the correct location from the first task.

Additional workspace assets

Copy task-manager.html to tasks/:

cp ${CLAUDE_PLUGIN_ROOT}/skills/tasks/task-manager/references/task-manager.html ~/Tandem/tasks/task-manager.html

Tell the user: "I've also set up a visual Kanban board — open task-manager.html in Chrome or Edge to see your tasks visually."

Create brand/ directory:

mkdir -p ~/Tandem/brand

This is where users will place brand assets (logo, PPTX template, guidelines PDF) for /setup-brand.

Copy dashboard to workspace root:

mkdir -p ~/Tandem/assets
cp ${CLAUDE_PLUGIN_ROOT}/skills/core/dashboard/assets/dashboard.html ~/Tandem/dashboard.html
cp ${CLAUDE_PLUGIN_ROOT}/skills/core/dashboard/assets/tabler.min.css ~/Tandem/assets/
cp ${CLAUDE_PLUGIN_ROOT}/skills/core/dashboard/assets/tabler.min.js ~/Tandem/assets/
cp ${CLAUDE_PLUGIN_ROOT}/skills/core/dashboard/assets/tabler.rtl.min.css ~/Tandem/assets/

Update the embedded JSON in dashboard.html with the user's name, language, and initial connector status from onboarding state.

6c. Confirm workspace creation

After creating all folders and files, show the user what was created:

"Your workspace is ready! Here's what I created:" / "סביבת העבודה שלך מוכנה! הנה מה שיצרתי:" / "Ваше рабочее пространство готово! Вот что я создал:"

List all created folders and briefly explain each one.

AskUserQuestion:

• "Looks great — continue" / "נראה מעולה — להמשיך" / "Отлично — продолжить"
• "I want to add more folders" / "אני רוצה להוסיף עוד תיקיות" / "Хочу добавить ещё папки"

If "add more" — run the subfolder skill for additional folders.

---

Task Format

When creating the initial kanban.md, follow the canonical format in tandem-skills/tasks/task-manager/references/kanban-format.md.

Key rules:

1. Read <!-- Config: Last Task ID: NNN --> from kanban.md to get the next ID
2. Increment the counter: if last ID was 005, next task is TASK-006
3. Write the updated counter back: <!-- Config: Last Task ID: 006 -->
4. Use canonical format: ### TASK-XXX | Title (H3, 3-digit zero-padded, pipe separator)
5. Meta on ONE line: **Priority**: X | **Category**: X | **Assigned**: @user

---

Handoff to Finalize

After the workspace is confirmed (user selects "Looks great — continue"):

Append to ~/Tandem/.onboarding-state.md:

workspace_created: true
workspace_path: ~/Tandem/

Then invoke the finalization phase:

Skill(skill="tandem:begin-finalize")