fc-assistant

Functional Consultant Skills

A set of skills for WAM Global's AI-powered Salesforce functional consultant, running in Claude Desktop. Covers the full engagement lifecycle — from pre-workshop preparation through solution design, formal documentation, UAT, and end-user training.

---

Overview

The functional consultant is responsible for leading discovery workshops with the client, analysing requirements, designing the Salesforce solution, producing the sign-off documentation, and preparing the testing and training materials.

These skills implement that role as a structured, phase-driven process. Each skill corresponds to a phase of the engagement. The orchestrator (fc-assistant) manages the lifecycle, enforces quality gates, and invokes the right skill at the right time.

---

Setup

Complete these steps once. You will not need to repeat them for future projects.

---

Step 1 — Install Claude Desktop

Download and install Claude Desktop from claude.ai/download. Sign in with your Anthropic account.

---

Step 2 — Install the FC Assistant skills

1. In Claude Desktop, open Settings
2. Go to Skills in the left panel
3. Click the + button next to Personal plugins
4. In the Add marketplace dialog, enter:

   wam-leadclic/functional-consultant-assistant-skills
   

5. Click Sync

This installs all 11 skills at once. You will not need to repeat this for future projects — only when there is a new version to update to.

---

Updating the skills

To update to a newer version, go to Settings → Skills, find the plugin, and click Sync again.

---

Step 3 — Connect to Atlassian (Confluence)

1. In Claude Desktop, click the Settings icon (bottom-left corner)
2. Go to Integrations
3. Find Atlassian and click Connect
4. A browser window will open — log in with your Atlassian account

If Atlassian does not appear in the Integrations list, contact your Atlassian administrator to confirm that the Rovo MCP integration is enabled for your organisation.

---

Step 4 — Connect to Google Drive (optional)

Only needed if commercial or workshop materials are stored in Google Drive.

1. In Claude Desktop Settings → Integrations
2. Find Google Drive and click Connect
3. Authenticate with your Google account when the browser opens

If all your project materials are stored locally in resources/, skip this step.

---

Step 5 — Download this repository (optional)

Only needed if you will store project materials locally in resources/commercial/ and resources/workshops/. If you will always provide materials via Google Drive, Confluence, or file attachments in the conversation, skip this step.

Download this repository as a ZIP from GitHub and unzip it on your computer, or clone it:

git clone https://github.com/wam-leadclic/functional-consultant-assistant-skills.git

---

Starting a new project engagement

Follow these steps at the beginning of each client engagement.

---

1. Create a new Project in Claude Desktop

Each client engagement gets its own Project. This keeps all conversations for that engagement together and maintains shared context across sessions.

1. In Claude Desktop, click + New Project in the sidebar
2. Name it after the client or engagement (e.g. Acme Corp — Salesforce CRM)

---

2. Start a conversation

Open a new conversation in the Project and type:

new project

Claude will read agent-params.md from the project folder. If it is missing or incomplete, Claude will ask you for the required details (project name, client, Confluence root page URL, language, integrations) and write the file automatically.

---

3. Add commercial materials

Place your pre-sales documents (proposals, SOW, RFPs, audit documents) in resources/commercial/. Alternatively, drag and drop files directly into the conversation or configure a Google Drive folder when Claude asks.

---

Engagement Lifecycle

Commercial materials (local folder, Google Drive, or Confluence)
        │
        ▼
[fc-workshop-prep]          Phase 1 — Workshop guide from commercial + client system materials
        │
        ▼
   WORKSHOPS
        │
        ▼
[fc-workshop-analysis]      Phase 2 — Requirements Register + FDRs + Integration Map
        │
        ▼
[fc-solution-design] ◄──── iterative FDR resolution
        │
        ▼
[fc-functional-document]    Phase 4 — Formal sign-off document
        │
        ├──► [fc-uat-generator]          Phase 4.5 — UAT plan + test cases (immediately after sign-off)
        │
        ├──► [fc-training-materials]     Phase 6 — Training per user profile
        │
        └──► [fc-architect-handoff]      Optional — Input package for architect AI agent

fc-scope-register, fc-fdr-format, and fc-change-log are cross-cutting utilities used throughout the lifecycle.