/workspace-builder

name: workspace-builder
description: Build a CRM workspace from scratch — describe your business and get boards, columns, and pipeline stages created in monday. Use when someone says "set up my CRM", "build me a CRM", "create CRM boards for me", "I need a new sales pipeline", "help me get started in monday", "I don't know how to set up my pipeline", or "build me a CRM from scratch". Do not use for questions about an existing board — those belong to daily-briefing or data-cleanup.
argument-hint: "[optional: business description, e.g. 'window coverings, B2C, ~50 leads/month']"
user-invocable: true
allowed-tools: [Read, WebFetch, AskUserQuestion, mcp__monday__get_user_context, mcp__monday__list_workspaces, mcp__monday__workspace_info, mcp__monday__search, mcp__monday__create_workspace, mcp__monday__create_board, mcp__monday__create_group, mcp__monday__create_column, mcp__monday__create_item, mcp__monday__create_doc, mcp__monday__get_board_info, mcp__monday__all_monday_api]
# all_monday_api scope: group rename (update_group), group delete (delete_group — confirmed Default mode only), status label config, number unit config. No other mutations.

Workspace Builder

Sets up a CRM workspace conversationally — turning "I don't know how to start" into a working board on day 1. Replaces the manual template-pick → column-rename → column-add → group-rename loop that gates 442 median days between CRM install and first MCP execution. **This is the single highest-leverage retention skill in the catalog.**

Flow: **Trigger → Discover → Propose → Confirm → Build (α) → Seed (β, opt-in) → Handoff**.

Input

• Optional: business description via argument.
• Optional: user pre-declared mode (Default / Silent / Proactive). Add "silently" or "skip confirmations" to your request to run in Silent mode. Silent mode builds without per-step confirmations.

Output

• **α (default):** One board (or set of boards) created in the user's chosen workspace. Boards carry the user's chosen names (no plugin prefix). Groups + columns scaffolded per the proposed structure. A `CRM Setup — <Mon DD>` doc summarizes what was created and what's next, with `Generated by Claude · <ISO timestamp>` + `<!-- claude-skill-id: workspace-builder -->` in the body.
• **β (Seed mode, opt-in):** 5–10 example items per board so the user can see the shape with data, not just empty columns. Each example item carries `Source = Claude` on a status column (auto-create the column with user confirm if missing) — no `[Example]` prefix on names.
• **Proactive extension:** Out of scope for v0.1 (automation creation requires `create_automation_rule`, not yet shipped). The setup doc includes a deep-link to the in-product Automation Recipes UI for that step.

Knowledge

• monday CRM entity board catalog + relationships (§ monday CRM Entity Boards).
• Industry → board-shape map (§ Step 3).
• Column-type repertoire (§ Step 4).
• Shared artifact conventions (§ Shared patterns).
• GraphQL mutations for group operations: `references/monday-graphql-mutations.md`.

Tools (MCP)

• `get_user_context` — resolve user + existing workspaces.
• `list_workspaces` / `workspace_info` — find a target workspace.
• `search` — confirm we aren't duplicating an existing CRM board.
• `create_workspace` — only if the user explicitly wants a new workspace.
• `create_board` — the core write.
• `create_group` — pipeline stages as groups (or as status labels — see Step 4).
• `create_column` — typed columns per the proposed schema.
• `create_item` — β seed items.
• `create_doc` — publish the setup summary doc.
• `all_monday_api` — group rename/delete mutations + column settings (status labels, number units) not exposed by wrapped tools. See `references/monday-graphql-mutations.md` for exact payloads.

Cross-skill handoffs

• **From none (entry point):** First-run user, in-product CTA route, or explicit ask.
• **To daily-briefing:** Once the board has at least 5 items with a stage column populated, suggest `/monday-crm:daily-briefing` to start the daily-ops loop.
• **To data-cleanup:** After 30 days of use, suggest `/monday-crm:data-cleanup` for a fill-rate audit.

---

monday CRM Entity Boards

monday CRM is built around five canonical entity board types. When proposing a workspace structure, use these as building blocks — don't invent custom schemas. Use the user's own terminology for board and column names, but match the underlying column types and group structure.

**Always propose Deals. Add other boards only when the user's description clearly signals the need.**

Deals — the pipeline board (always included)

Every monday CRM user starts here.

• **Groups (pipeline stages):** New · Discovery · Proposal · Negotiation · Won · Lost
• **Columns:** Stage (status, `is_done: true` on Won), Owner (people), Deal Value (numbers $), Probability (numbers %), Expected Close (date), Last Touch (date), Source (status), Notes (long_text)

Contacts — individual people records

Add when the user mentions tracking people, contacts, or has account managers / a team managing relationships.

• **Groups:** Active · Inactive
• **Columns:** Email (email), Phone (phone), Company (text), Owner (people), Source (status), Last Activity (date), Notes (long_text)
• **Relates to:** Deals (link contact to their deal via board_relation)

Leads — inbound / unqualified prospects

Add when the user mentions SDR, outbound, lead gen, or has a qualification step before deals.

• **Groups:** New · Contacted · Qualified · Disqualified
• **Columns:** Stage (status), Owner (people), Source (status), Email (email), Phone (phone), Company (text), Last Touch (date), Notes (long_text)
• **Relates to:** Deals (qualified leads become deals — link via board_relation)

Accounts — companies / organizations

Add when the user mentions account management, renewals, B2B with multiple contacts per company, or CSM workflows.

• **Groups:** Active Customers · Prospects · Churned
• **Columns:** Owner (peo