fc-training-materials - SKILL.md Agent Skill

name: fc-training-materials description: Generates profile-specific end-user training materials from the Functional Document and UAT results. Produces user guides, quick reference cards, and scenario-based exercises in plain business language. No Salesforce jargon. tools: - Atlassian

Training Materials Generator

Generates profile-specific end-user training materials from the Functional Document and UAT plan. Covers user guides, quick reference cards, and scenario-based exercises. Written for the actual end user — not the consultant.

Purpose

Training materials determine adoption. Each profile gets only what is relevant to their daily work, written in the client's own language. Salesforce terminology never appears in user-facing materials. If the client calls "Accounts" something else, that term is used everywhere.

Inputs

Functional Document (Confluence) — defines what each profile does in the system. Required.
Solution Overview (Confluence) — process context for each functional area. Required.
UAT Plan (Confluence) — test cases adapted as training exercises. Optional. If available, test cases are reframed as scenario-based exercises. If not yet available, exercises are generated from the Solution Overview process descriptions instead.
List of target profiles — specific profiles or "all". Required.

Execution Steps

Step 0 — Read project configuration

Read agent-params.md from the root of the user's workspace folder. There is exactly one agent-params.md per project; it always lives at the root. Do not search subdirectories.

Extract:

Output language — all training materials must be generated in this language, including section headings and labels
Project name and Client — used in document headers
Confluence coordinates (Space key, Project root page ID) — publish targets

All training materials are published to the existing Training Materials skeleton page in Confluence, under the Deliverables section. Do not create local files.

Step 1 — Profile Analysis

For each target profile identified in the Functional Document, extract:

Technical Level: Low (first-time system users) | Medium (comfortable with business software) | High (power users, admins)

Training Priority is determined by role criticality to go-live and frequency of system use.

Step 2 — Content Plan

Before generating any materials, produce a training content plan and present it for confirmation:

# Training Content Plan — [Project Name]

| Profile | Modules | Documents | Priority |
|---|---|---|---|
| Sales Rep | Lead Management, Opportunity Management | User Guide, Quick Ref | High |

Do not generate materials until the content plan is confirmed.

Step 3 — Generate Materials Per Profile

Produce three document types for each profile.

A. User Guide — Comprehensive, task-oriented, step-by-step

# [Profile] User Guide — [System Name]
Version: 1.0 | Date: [date] | Prepared by: WAM Global

## Welcome
[2–3 sentences: what this system does for this user and why it matters to their work]

## Your Role
[What this profile is responsible for in the system. What they are NOT responsible for.]

## Getting Started
[Login, home page, key navigation, where to find daily work]

## [Module N]: [Task / Process Name]
### When to use this
### How to do it
[Numbered steps. Specific. What to click, what to enter, what to expect.]
### Tips and shortcuts
### Common mistakes

## Frequently Asked Questions
[Questions that came up in workshops or UAT — not generic FAQ filler]

B. Quick Reference Card — Maximum one printed page

# Quick Reference — [Profile Name] — [System Name]

## Your [N] key tasks:

### [Task 1]
1. [Step]
2. [Step]

### [Task 2]
...

If the content does not fit on one page, reduce scope to the three most frequent tasks. A quick reference card that requires scrolling is not a quick reference card.

C. Scenario-Based Exercises — Adapted from UAT test cases

If UAT Plan is available: Adapt Happy Path and Alternate Path test cases for this profile as described below.

If UAT Plan is not yet available: Generate scenario-based exercises from the TO-BE process steps in the Solution Overview for this profile. Use the same business scenario format — "You receive a call from a customer asking about..." — and end with "What do you do?" and "What does the system show?" Include the expected outcome as described in the process design.

For each Happy Path and Alternate Path test case relevant to this profile:

Reframe as a business scenario: "You receive a call from a customer asking about..."
Remove pass/fail framing entirely
End with: "What do you do?" and "What does the system show?"
Include the expected outcome as a learning confirmation, not a grading criterion

Step 4 — Shared Glossary

After all profile materials are generated, compile a shared glossary mapping Salesforce terms to client-specific business terms:

| Salesforce Term | What We Call It at [Client] | Plain Definition |

The glossary is the reference for consistent terminology across all materials. If a term was used differently in two profiles' materials, reconcile it here.

Step 5 — Regeneration Mode (after scope changes)

Invoked when a Change Log entry has flagged training modules as Needs Update — CL-[NNN].

Read the CL entry from the Change Log to understand what changed.
Identify all training documents (User Guides, Quick Reference Cards, Exercises) flagged for this CL-ID.
For each flagged document:
- Update only the sections affected by the change. Do not regenerate the entire document.
- Add a version note at the top of the updated document: Updated [date] — CL-[NNN]: [one-line description of change]
Update the Shared Glossary if the change introduced or modified terminology.
Confirm to the consultant:

"Training materials updated for CL-[NNN]. [N] documents revised across [N] profiles."

Writing Rules

No Salesforce jargon in user-facing materials. Never use: object, record, field, lookup, picklist, Opportunity, Lead, Account (unless the client uses that exact term). Use whatever the client calls these things. If unsure, check the Functional Document glossary.
Action-oriented headings. "How to create a new enquiry" — not "Enquiry creation".
Consistent terminology. Use the client's terms throughout all materials, across all profiles. The glossary enforces this.
Profile isolation. A sales rep's guide never mentions what the manager sees or can do, and vice versa.
Short modules. If a module exceeds one page, split it into two separate tasks.
Screenshots. Mark placeholder positions with [SCREENSHOT: what to show here]. Do not describe screenshot content in prose — the placeholder is sufficient.
Tone. Direct and helpful. Write as if explaining to a competent person who is new to this system. No condescension, no over-explanation of obvious steps.
Language: Write all materials in the language specified in agent-params.md. Use the client's own terminology throughout — check the Functional Document glossary for client-specific terms.

Publishing

Publish all materials to Confluence under "Deliverables / Training Materials":

One page per document type per profile: User Guide, Quick Reference, Exercises
Shared Glossary at: "Deliverables / Training Materials / Glossary"
Name pages consistently: [Profile] — User Guide, [Profile] — Quick Reference, [Profile] — Exercises