본문으로 건너뛰기
cccskills
무료GitHub에 공개

capa-officer

CAPA system management for medical device QMS — root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane스타 3(GitHub 3 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(5)

  • SKILL.md4.3 KB
  • references/effectiveness-verification-guide.md13.3 KB
  • references/rca-methodologies.md15.4 KB
  • scripts/capa_tracker.py20.5 KB
  • scripts/root_cause_analyzer.py17.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

CAPA Officer

Corrective and Preventive Action (CAPA) management within Quality Management Systems.

CAPA Investigation Workflow

  1. Document trigger event with objective evidence
  2. Assess significance and determine CAPA necessity
  3. Form investigation team with relevant expertise
  4. Collect data and evidence systematically
  5. Select and apply appropriate RCA methodology
  6. Identify root cause(s) with supporting evidence
  7. Develop corrective and preventive actions
  8. Validation: Root cause explains all symptoms; if eliminated, problem would not recur

CAPA Necessity Determination

Trigger TypeCAPA RequiredCriteria
Customer complaint (safety)YesAny involving patient/user safety
Internal audit finding (Major)YesSystematic failure or absence
Nonconformance (recurring)YesSame NC type 3+ times
External audit findingYesAll Major and Minor findings
Customer complaint (quality)EvaluateBased on severity and frequency
Trend analysisEvaluateBased on significance

Root Cause Analysis

Select methodology based on problem characteristics:

  • 5 Why Analysis — Single-cause issues with linear causation
  • Fishbone Diagram (6M) — Complex systemic issues with 3-6 factors
  • Fault Tree Analysis — Safety-critical or system reliability issues
  • Human Factors Analysis — Human error as suspected primary cause
  • FMEA — Proactive risk assessment

Root Cause Validation Checklist

  • Root cause verified with objective evidence
  • If eliminated, problem would not recur
  • Within organizational control
  • Explains all observed symptoms

For complete RCA method details, decision tree, 5-Why template with example, and fishbone categories, see references/rca-methodologies.md.


Corrective Action Planning

TypePurposeTimeline
ContainmentStop immediate impact24-72 hours
CorrectionFix specific occurrence1-2 weeks
CorrectiveEliminate root cause30-90 days
PreventivePrevent in other areas60-120 days

For action plan template, effectiveness indicators, and implementation timeline, see references/effectiveness-verification-guide.md.


Effectiveness Verification

  1. Allow adequate implementation period (30-90 days minimum)
  2. Collect post-implementation data
  3. Compare to pre-implementation baseline
  4. Evaluate against success criteria
  5. Verify no recurrence during verification period
  6. Validation: All criteria met with objective evidence

Verification Timeline

CAPA SeverityWait PeriodVerification Window
Critical30 days30-90 days
Major60 days60-180 days
Minor90 days90-365 days

For verification methods, effectiveness determination decision tree, and closure requirements, see references/effectiveness-verification-guide.md.


CAPA Metrics

MetricTarget
CAPA cycle time<60 days average
Overdue rate<10%
First-time effectiveness>90%
Recurrence rate<5%

Tools and References

ToolPurpose
capa_tracker.pyGenerate CAPA status reports and metrics
DocumentContent
rca-methodologies.md5-Why, Fishbone, FTA, Human Factors, FMEA templates
effectiveness-verification-guide.mdVerification planning, methods, action plans, closure

Regulatory Requirements

ISO 13485:2016 Clause 8.5

  • 8.5.2 Corrective Action: Eliminate cause of nonconformity
  • 8.5.3 Preventive Action: Eliminate potential nonconformity

FDA 21 CFR 820.100

Required elements: procedures, quality data analysis, cause investigation, action identification, effectiveness verification, management review submission.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

SebastianLuser의 스킬 모두 보기

이 스킬의 문제 신고