Training Plan
Design a legal compliance training program for "$ARGUMENTS". Identify training needs by role, design training modules, set cadence and tracking, and plan delivery methods.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"legal-training-plan","workflow":"legal","phase":4,"project":"<project>","event":"skipped","artifact":"04-govern.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 4 (Govern) of the Legal Lifecycle workflow (legal); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or legal when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"legal-training-plan","workflow":"legal","phase":4,"project":"<project>","event":"refused","artifact":"04-govern.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"legal-training-plan","workflow":"legal","phase":4,"project":"<project>","event":"started","artifact":"04-govern.md","note":""}.
Check that .singularskills/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g.
/legal-risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
Read inputs:
- Read
.singularskills/legal/<project>/00-assess.mdfor risk context, applicable regulations, and organizational profile - Review any existing compliance artifacts in
.singularskills/legal/<project>/
- Read
Identify training needs by role:
- All employees:
- Data protection basics (handling personal data, recognizing data breaches)
- Confidentiality obligations (trade secrets, proprietary information)
- Code of conduct and ethics
- Reporting procedures (whistleblower channels, incident reporting)
- Engineering:
- Open-source license compliance (permissive vs. copyleft, attribution requirements)
- Security practices (secure coding, vulnerability handling, access controls)
- Data handling in development (test data, production data separation)
- IP considerations (invention assignments, prior art awareness)
- Sales:
- Contract terms they can and cannot negotiate
- NDA procedures and standard terms
- Anti-bribery and anti-corruption basics
- Competition law essentials (pricing discussions, market allocation)
- HR:
- Employment law basics (hiring, termination, documentation)
- Discrimination and harassment prevention and response
- Leave and accommodation requirements
- Employee data privacy
- Procurement:
- Vendor assessment and due diligence requirements
- Contract review fundamentals
- Conflict of interest policies
- Supply chain compliance obligations
- All employees:
Design training modules with learning objectives:
- For each module, define:
- Title — clear, descriptive module name
- Target audience — which roles must complete this module
- Learning objectives — specific, measurable outcomes (e.g., "Identify the three types of personal data under GDPR")
- Duration — estimated time to complete
- Content outline — key topics covered
- Practical exercises — scenarios, case studies, or simulations
- For each module, define:
Set training cadence:
- Onboarding — required modules completed within first 30 days of employment
- Annual refresh — mandatory annual recertification on core compliance topics
- Event-triggered training — additional training required when:
- New regulations take effect
- A compliance incident occurs
- Role changes require new competencies
- Policy updates are implemented
- Define grace periods and consequences for non-completion
Define completion tracking and certification:
- Track completion status per employee per module
- Issue certificates of completion with expiration dates
- Generate compliance reports showing organization-wide training status
- Set minimum passing scores for assessments
- Maintain audit-ready training records
Create assessment questions per module:
- Develop knowledge-check questions aligned with learning objectives
- Include scenario-based questions testing practical application
- Mix question formats (multiple choice, true/false, scenario response)
- Define passing threshold (recommended: 80% minimum)
- Create question pool for randomized assessments
Identify delivery method per module:
- E-learning — self-paced online modules for foundational topics
- Live workshop — interactive sessions for complex or discussion-heavy topics
- Documentation — reference guides and quick-reference cards for ongoing use
- Micro-learning — short, focused content for specific updates or reminders
- Match delivery method to content complexity and audience needs
Plan regulatory-specific training:
- GDPR awareness — data subject rights, lawful bases, cross-border transfers
- CCPA requirements — consumer rights, opt-out mechanisms, service provider obligations
- SOC 2 controls — security policies, access management, incident response
- Accessibility (WCAG) — accessible design principles, testing procedures, remediation
- Tailor regulatory training depth to each role's exposure level
Write the artifact — append to
.singularskills/legal/<project>/04-govern.mdunder a## Training Plansection. Create the file with a# Govern — <project>heading if it does not exist; if a## Training Plansection already exists, replace only that section. The section contains:- Training Needs Matrix — role-based training requirements
- Module Catalog — all training modules with objectives and durations
- Training Cadence — schedule for onboarding, refresh, and event-triggered training
- Tracking and Certification — completion tracking approach and reporting
- Assessment Framework — sample questions and passing criteria per module
- Delivery Methods — method selection rationale per module
- Regulatory Training Plan — regulation-specific training details
Output
The training plan appended to .singularskills/legal/<project>/04-govern.md. Present a summary to the user highlighting:
- Total number of training modules and their target audiences
- Training cadence overview (onboarding, annual, event-triggered)
- Key regulatory training requirements
- Recommended delivery methods and tracking approach
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"legal-training-plan","workflow":"legal","phase":4,"project":"<project>","event":"finished","artifact":"04-govern.md","note":""}.
This artifact is shared by every skill of phase 4 (Govern). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Govern
workflow: legal
phase: 4
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Training Plan section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is legal-training-plan).
End your section with ### Decisions and ### Open questions (one level under your ## Training Plan heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>