quality-capa

Manages the CAPA lifecycle with 5 Whys root cause analysis and aging dashboards.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill quality-capa-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-capa
Source: https://github.com/tapway/shogun-os/tree/main/skills/manufacturing/quality-capa
Command: npx skills add https://github.com/tapway/shogun-os --skill quality-capa-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manufacturing quality teams struggle to track corrective and preventive actions from identification through closure, often losing sight of root causes, overdue actions, and whether fixes actually prevented recurrence. ## Core Features & Use Cases - Six-Phase CAPA Lifecycle: Tracks CAPAs through Open, Investigation, Action Plan, Implementation, Effectiveness Check, and Closed phases with severity-based closure targets. - 5 Whys Root Cause Analysis: Guides structured interactive root cause investigation before action planning begins. - Aging and Closure Dashboards: Reports aging distribution, closure rates by severity and department, and auto-escalates CAPAs exceeding configured phase time limits. - Use Case: A quality engineer receives a recurring dimension defect NCR, creates a major-severity CAPA linked to that NCR, runs a 5 Whys session to find worn tooling as the root cause, assigns corrective actions to named owners, and verifies effectiveness after 90 days. ## Quick Start Ask the agent to create a CAPA from NCR-2026-001234 with major severity for a recurring dimension defect on line A.

Frequently Asked Questions about quality-capa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a CAPA from an NCR?

Run the create subcommand with the source type, source ID, severity, and description, for example: create --source ncr --source-id NCR-001 --severity major --description "Recurring dimension defect". The script returns a CAPA record with a generated ID, phase set to open, and a severity-based closure target.

How does 5 Whys root cause analysis work in a CAPA workflow?

The 5whys subcommand generates a structured worksheet with five guided why levels, a problem statement field, and a root cause capture field. It supports an interactive mode and references a configurable template path via CAPA_5WHYS_TEMPLATE_PATH.

What severity levels does CAPA classification support?

Four severity levels are supported: critical (14-day closure target), major (30 days), minor (60 days), and observation (90 days). Invalid severity values are rejected with an error listing the valid options.

When should I not create a CAPA for a quality issue?

Do not create CAPAs for one-off defect dispositioning, which belongs in an NCR workflow, or for minor observations below the severity threshold. Creating CAPAs for every minor issue dilutes focus and inflates the backlog.

Why is my CAPA effectiveness check invalid?

Effectiveness checks fail when performed too early, before enough data accumulates, or too late after process drift. The skill enforces a configurable wait period via CAPA_EFFECTIVENESS_WAIT_DAYS, defaulting to 90 days, before verification.