How to set up your first workspace in Worklayer

Use Case: When you're starting with Worklayer for the first time and need a structured workspace Time to Complete: 10 minutes Prerequisites: Worklayer installed, Claude account (API or Pro)

Quick Answer

In Worklayer, you can set up your first workspace in 10 minutes by creating a workspace folder, adding basic context files, and connecting your first tool (like Jira). This gives you a foundation for AI-assisted PM work.

Step-by-Step Instructions

Step 1: Create Workspace Folder

Create a new folder on your Mac for your workspace. This will hold all your product context, templates, and outcomes.

Example:

Create folder: ~/Documents/my-product-workspace

Open this folder in Worklayer via File → Open Workspace or drag the folder into Worklayer.

Step 2: Add Basic Context Files

Create a Context/ folder and add your first context files: company goals, product features, and personas.

Example structure:

my-product-workspace/
├── Context/
│   ├── Company/
│   │   └── goals-and-okrs.md
│   ├── Product/
│   │   ├── personas-and-use-cases.md
│   │   └── product-features.md
├── Templates/
│   └── Work/
├── Outcomes/
    ├── PRDs/
    ├── UserStories/
    └── Reports/

You can use AI to help populate these files (see "How to organize product context in Worklayer").

Step 3: Add Templates

Create a Templates/Work/ folder and add starter templates for common deliverables.

Example templates:

prd-template.md (for product requirements)
user-story-template.md (for sprint planning)
stakeholder-update-template.md (for weekly updates)

Worklayer's starter workspaces include example templates you can customize.

Step 4: Connect Your First Tool (Optional)

If you use Jira, Linear, or Slack, connect one tool via MCP Manager.

Example:

Click Home → Add MCP
Select Jira connector
Paste API token
Test connection

This enables AI to pull live data from your tools.

Step 5: Test the Workflow

Create your first deliverable to verify everything works.

Example test:

Use @Context/Product/personas-and-use-cases.md and @Templates/Work/prd-template.md to draft a sample PRD for a test feature.

If AI can read your context files and template, your workspace is ready.

Example: End-to-End Workflow

Let's set up a workspace for "Worklayer Product Management."

Step 1: Create folder ~/Documents/worklayer-pm-workspace

Step 2: Create folder structure:

worklayer-pm-workspace/
├── Context/
│   ├── Company/
│   └── Product/
├── Templates/
│   └── Work/
├── Outcomes/

Step 3: Add first context file using AI:

Go to worklayer.pro and gather information about Worklayer's product, features, and target users. Create Context/Product/product-overview.md with this information.

Step 4: Add PRD template:

Create a PRD template at Templates/Work/prd-template.md with sections: Executive Summary, Problem Statement, Success Metrics, User Stories, Rollout Plan.

Step 5: Test workflow:

Use @Context/Product/product-overview.md and @Templates/Work/prd-template.md to draft a sample PRD for "Task Status Management Feature."

Result: AI generates a PRD using your context. Workspace is ready.

Time to set up: 10 minutes

Tips & Best Practices

Start minimal: Don't create 20 context files on day one. Start with 2-3 files (goals, personas, features) and expand as needed.
Use AI to populate context: Instead of manually writing context files, ask AI to research your product (from website, docs, or existing files) and create context files for you.
Create folder structure early: Set up Context/, Templates/, and Outcomes/ folders from the start. This keeps your workspace organized as it grows.
Connect one tool first: Don't connect every tool immediately. Start with Jira or Linear (whichever you use most) and add others later.
Test before building: Run a test workflow (create a sample PRD or user story) to verify context files and templates work before investing more time.

Common Mistakes to Avoid

Creating too many context files: If you create 15 context files on day one, you'll spend more time organizing than working. Start with 2-3 core files.
Not testing the workflow: Don't assume your workspace is ready. Test by creating a sample deliverable to verify AI can read your context and templates.
Skipping folder structure: If you don't create Context/, Templates/, and Outcomes/ folders upfront, your workspace becomes messy quickly. Set up structure early.