design-training-program
Acerca de
Esta habilidad diseña programas integrales de capacitación GxP para cumplimiento, abarcando análisis de necesidades, diseño curricular y criterios de evaluación. Se utiliza al implementar nuevos sistemas, abordar hallazgos de auditoría o prepararse para inspecciones. Los resultados clave incluyen planes de capacitación basados en roles y desencadenantes definidos de recertificación ante cambios en los procedimientos operativos estándar.
Instalación rápida
Claude Code
Recomendadonpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/design-training-programCopia y pega este comando en Claude Code para instalar esta habilidad
Documentación
Design Training Program
Role-based GxP training programme. Curriculum, competency assessments, record management for regulated env.
When Use
- New validated system needs user training before go-live
- Audit finding cites bad training or missing training records
- Org changes bring new roles or responsibilities
- Periodic review of training programme due
- Regulatory inspection prep needs proof of training adequacy
Inputs
- Required: Systems + processes needing trained personnel
- Required: Role definitions (admin, user, QA, management)
- Required: Regulatory training requirements (GMP, GLP, GCP)
- Optional: Existing training materials or curricula
- Optional: Competency gaps from audits or perf reviews
- Optional: Training management system capabilities
Steps
Step 1: Do Training Needs Analysis
Find what each role needs to know:
# Training Needs Analysis
## Document ID: TNA-[DEPT]-[YYYY]-[NNN]
### Role-Based Training Requirements
| Role | GxP Awareness | System Training | Data Integrity | SOP Training | Assessment Type |
|------|--------------|----------------|----------------|--------------|-----------------|
| System Administrator | Advanced | Advanced | Advanced | Admin SOPs | Written + Practical |
| End User | Basic | Intermediate | Intermediate | Operational SOPs | Written + Practical |
| QA Reviewer | Advanced | Basic (review focus) | Advanced | QA SOPs | Written |
| Management | Basic | Overview only | Intermediate | Governance SOPs | Written |
| IT Support | Basic | Infrastructure only | Basic | IT SOPs | Written |
### Training Gap Analysis
| Role | Current Competency | Required Competency | Gap | Priority |
|------|-------------------|---------------------|-----|----------|
| [Role] | [Current level] | [Required level] | [Gap description] | [H/M/L] |
Got: Every role has training needs linked to job function + GxP responsibilities.
If fail: Roles unclear? Do RACI first. Set responsibilities before training needs.
Step 2: Design Curriculum
Break training into modules by topic:
# Training Curriculum
## Document ID: TC-[DEPT]-[YYYY]-[NNN]
### Module 1: GxP Regulatory Awareness
**Duration:** 2 hours | **Delivery:** Classroom / eLearning | **Audience:** All roles
**Content:**
1. Introduction to GxP regulations (GMP, GLP, GCP overview)
2. 21 CFR Part 11 and EU Annex 11 requirements for electronic records
3. Data integrity principles (ALCOA+)
4. Consequences of non-compliance (warning letters, consent decrees, product recalls)
5. Individual responsibilities and accountability
### Module 2: System-Specific Training — [System Name]
**Duration:** 4 hours | **Delivery:** Instructor-led with hands-on | **Audience:** Users, Admins
**Content:**
1. System purpose and GxP classification
2. Login, navigation, and role-based access
3. Core workflows (step-by-step for each user task)
4. Electronic signature procedures
5. Audit trail: how entries are created and what they mean
6. Error handling and deviation reporting
7. Data entry best practices
### Module 3: Data Integrity in Practice
**Duration:** 1.5 hours | **Delivery:** Workshop | **Audience:** Users, QA, Admins
**Content:**
1. ALCOA+ principles with system-specific examples
2. Common data integrity risks and how to avoid them
3. Recognising and reporting data integrity concerns
4. Audit trail review basics
5. Case studies: real-world data integrity failures and lessons learned
### Module 4: SOP Training — [SOP-ID]
**Duration:** 1 hour per SOP | **Delivery:** Read and sign / walkthrough | **Audience:** Per SOP scope
**Content:**
1. SOP purpose and scope
2. Step-by-step procedure walkthrough
3. Decision points and deviation handling
4. Forms and documentation requirements
5. Q&A and clarification
Got: Each module: duration, delivery method, audience, content outline.
If fail: Content too broad for time? Split into sub-modules or prerequisite chains.
Step 3: Make Competency Assessments
Define how competency measured per module:
# Competency Assessment Design
### Assessment Types
| Type | When to Use | Passing Score | Records |
|------|------------|---------------|---------|
| **Written test** | Knowledge assessment (regulations, principles) | 80% | Score sheet retained |
| **Practical demonstration** | Skill assessment (system operation) | All critical steps correct | Signed observation form |
| **Observed task** | On-the-job competency | Supervisor sign-off | Competency form |
### Sample Written Assessment — GxP Awareness (Module 1)
1. List the five ALCOA principles for data integrity. (5 points)
2. Under 21 CFR 11.50, what three elements must an electronic signature display? (3 points)
3. You discover that a colleague's data entry contains an error. Describe the correct procedure to correct it. (5 points)
4. True/False: A shared login account can be used if all users sign a logbook. (2 points — answer: False)
5. Describe one consequence of a data integrity failure for a pharmaceutical company. (5 points)
**Passing score:** 16/20 (80%)
**On failure:** Retraining required before re-assessment. Maximum 2 re-attempts.
### Practical Assessment Template
| Step | Task | Observed? | Performed Correctly? | Comments |
|------|------|-----------|---------------------|----------|
| 1 | Log in with personal credentials | Yes/No | Yes/No | |
| 2 | Navigate to [specific function] | Yes/No | Yes/No | |
| 3 | Enter test data correctly | Yes/No | Yes/No | |
| 4 | Apply electronic signature | Yes/No | Yes/No | |
| 5 | Locate and interpret audit trail | Yes/No | Yes/No | |
**Assessor:** _______ **Date:** _______ **Result:** Pass / Fail
Got: Assessments test knowledge (why) + skill (how).
If fail: Pass rates < 70%? Review training materials for clarity before blaming learners.
Step 4: Define Training Records + Retention
# Training Record Management
### Required Training Records
| Record | Format | Retention Period | Storage |
|--------|--------|-----------------|---------|
| Training matrix (who needs what) | Electronic | Current + 2 years superseded | Training management system |
| Individual training transcript | Electronic | Employment + 2 years | Training management system |
| Assessment results | Electronic or paper | Same as transcript | Training management system |
| Training materials (version used) | Electronic | Life of system + 1 year | Document management system |
| Trainer qualification records | Electronic | Employment + 2 years | HR system |
### Training Matrix Template
| Employee | Role | Module 1 | Module 2 | Module 3 | SOP-001 | SOP-002 | Status |
|----------|------|----------|----------|----------|---------|---------|--------|
| J. Smith | User | 2026-01-15 ✓ | 2026-01-16 ✓ | Due 2026-03-01 | 2026-01-20 ✓ | N/A | Partially trained |
| K. Jones | Admin | 2026-01-15 ✓ | 2026-01-17 ✓ | 2026-01-18 ✓ | 2026-01-20 ✓ | 2026-01-20 ✓ | Fully trained |
Got: Training records show every person doing GxP activity was trained + assessed before.
If fail: Training records incomplete? Do retrospective training gap assessment. Immediate remediation training.
Step 5: Define Retraining Triggers
# Retraining Triggers
| Trigger | Scope | Timeline | Assessment Required? |
|---------|-------|----------|---------------------|
| SOP revision (minor) | Affected users — read and sign | Before new version effective | No — read and acknowledge |
| SOP revision (major) | Affected users — formal retraining | Before new version effective | Yes — written or practical |
| System upgrade | All users of affected functionality | Before production go-live | Yes — practical demonstration |
| Data integrity incident | Involved personnel + department | Within 30 days of investigation closure | Yes — written |
| Audit finding (training-related) | Per CAPA scope | Per CAPA timeline | Per CAPA requirements |
| Annual refresher | All GxP personnel | Annual from initial training date | No — refresher acknowledgement |
| Role change | Individual | Before assuming new responsibilities | Yes — per new role requirements |
| Extended absence (>6 months) | Returning individual | Before resuming GxP activities | Yes — practical assessment |
Got: Retraining triggers specific, measurable, linked to timelines.
If fail: Retraining not done before trigger deadline? Individual must NOT do affected GxP activities until training done.
Step 6: Compile Training Programme Doc
# Training Programme
## Document ID: TRAINING-PROGRAM-[DEPT]-[YYYY]-[NNN]
### 1. Purpose and Scope
### 2. Training Needs Analysis [Step 1]
### 3. Curriculum [Step 2]
### 4. Competency Assessments [Step 3]
### 5. Training Records and Retention [Step 4]
### 6. Retraining Triggers [Step 5]
### 7. Programme Review
- Annual review of training effectiveness (pass rates, audit findings, incidents)
- Curriculum update when systems, SOPs, or regulations change
- Trainer qualification verification
### 8. Approval
| Role | Name | Signature | Date |
|------|------|-----------|------|
| Training Manager | | | |
| QA Director | | | |
| Department Head | | | |
Got: Training programme approved + effective before system go-live or compliance deadline.
If fail: Approval delayed? Interim training measures, document the formalisation plan.
Checks
- Training needs analysis done for all roles touching GxP systems
- Curriculum modules defined: duration, delivery, content outline
- Competency assessments exist per module, defined passing criteria
- Training matrix tracks all personnel vs all required training
- Training record retention meets regulatory needs
- Retraining triggers defined: timelines + assessment needs
- Training programme approved by QA + management
Pitfalls
- Training = reading the SOP: Read-and-sign fits minor updates, not initial training. New users need instructor-led + hands-on.
- No competency assessment: Training without assessment can't prove learning. Regulators expect competence evidence, not attendance.
- Trainer not qualified: Trainers must be demonstrably competent. "Train the trainer" records often asked in inspections.
- Stale training matrix: Not updated when people join/leave/change roles → compliance gaps. Integrate with HR.
- One-size-fits-all: Admins need deeper training than end users. Role-based curriculum avoids overwhelming some, under-training others.
See Also
write-standard-operating-procedure— SOPs drive training content + retraining triggersdesign-compliance-architecture— shows which systems + roles need trainingconduct-gxp-audit— audits often check training adequacymanage-change-control— system changes trigger retrainingprepare-inspection-readiness— training records = primary inspection target
Repositorio GitHub
Habilidades relacionadas
executing-plans
DiseñoUtilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.
requesting-code-review
DiseñoEsta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.
connect-mcp-server
DiseñoEsta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.
web-cli-teleport
DiseñoEsta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.
