Lesson 6 of 7 / HQ fundamentals

Resume, Hand Off, and Collaborate on a Project

Scope a session to a company and project, capture an early brainstorm, save it with a handoff, and let a teammate resume the same work elsewhere.

Begin lesson

Complete in: 8–10 minutes, excluding sync latency
Written path: 7 steps

Outcome

You will create durable project context that another authorized teammate can load from a fresh session on another computer.

Recorded walkthrough

Watch the complete path.

Follow the recording once, then use the written steps below as the durable checklist. English captions are available from the player controls.

HQ / Tutorial recording

This walkthrough uses demo data and shows the complete recorded workflow. Use the written steps below as your durable checklist while you follow along.

Before You Begin

HQ is installed and the company is available in your workspace.
The teammate has already joined the company and can access its shared project state.
Cloud/team synchronization is active on both computers.

Step 1
Use the recommended session lifecycle
Begin with a clear scope, do the work, and finish with a handoff so context remains organized and recoverable.
CommandRun exactly as shown
```
> /startwork → work → /handoff
```
Expected result
You understand that the lifecycle improves continuity even though HQ can operate without it.
Step 2
Start a company-scoped session
Run Startwork with the company, project, or repository you intend to use. The recording begins at company scope.
CommandRun exactly as shown
```
> /startwork awesomeco
```
Expected result
HQ sets the session company and reads its relevant context.
Field note
awesomeco is the recording's example company handle; replace it for real work.
Step 3
Describe the project and brainstorm
Describe the project in plain language and choose the lightweight brainstorm path while the idea is still rough.
PromptSend in your AI session
```
› I want to create a new project called lead generation, where we automate the process of managing our leads.
› Choose the brainstorm option
```
Expected result
HQ creates a project brainstorm with context, knowns, unknowns, and possible approaches.
Field note
Lead Generation is the demonstration project, not a required project name.
Step 4
Stop cleanly with a handoff
When you decide to pause, run the handoff instead of abandoning the open session.
CommandRun exactly as shown
```
> /handoff
```
Expected result
HQ saves durable context, updates knowledge, and records version history for recovery.
Step 5
Confirm the project artifacts
Open the company project in the Vault and verify that the journal and brainstorm were saved.
NavigationOpen this destination
```
→ Inspect the project journal and brainstorm.md
```
Expected result
The project contains a journal area and a durable brainstorm.md file.
Step 6
Resume from the teammate's session
On the other computer, scope a fresh session to both the company and project, then ask for a status update.
CommandRun exactly as shown
```
> /startwork awesomeco lead-gen
> A teammate asked me to pick up the lead generation project. Please update me.
```
Expected result
HQ locates the synchronized Lead Generation project from the first session.
Field note
awesomeco and lead-gen are the exact example handles in the recording; use your authorized handles in real work.
Step 7
Verify project binding
Let Startwork finish reading the project before continuing, then confirm it found the earlier brainstorm.
Expected result
The teammate sees the prior brainstorm and the new session is bound to the shared project.

Observable finish line

You are done when this is true.

The first session saves a project journal and brainstorm.md, and the teammate's fresh /startwork awesomeco lead-gen session reads that context and binds to the same project.