FREE CLAUDE & CODEX PLUGIN TEMPLATE
A real SOT-based Quality Management System (QMS) PRD template connecting quality standard, inspection plan, inspection result, nonconformance, and capa registration, inspection, defect, nonconformance, corrective action, audit, and document-history lookup, inspection execution, nonconformance classification, root-cause analysis, capa approval, effectiveness validation, and closure handling, defect rate, nonconformance, capa due date, audit, and cost-of-quality reporting.
View source on GitHub · MIT licensed
USE CASE
Teams designing an internal operations system for quality practitioner and shop-floor worker managing quality standards and inspection results and qms and quality-assurance operations coordinator
CONTENTS
VIBESPEC VIEWER
Each screen is generated from the public SOT included with this template.
Open this screen in the live demo 
Open this screen in the live demo 
Open this screen in the live demo 
Open this screen in the live demo PRACTICAL GUIDE
This Quality Management System (QMS) connects quality standard, inspection plan, inspection result, nonconformance, and capa registration, inspection, defect, nonconformance, corrective action, audit, and document-history lookup, inspection execution, nonconformance classification, root-cause analysis, capa approval, effectiveness validation, and closure handling, and defect rate, nonconformance, capa due date, audit, and cost-of-quality reporting in one SOT-based planning document. Use the complete HTML to review and share the plan, then adapt the SOT JSON with the VibeSpec plugin in Claude or Codex.
For quality standard, inspection plan, inspection result, nonconformance, and capa registration, define the required context, classification rules, and duplicate or missing-data checks before work enters the operating queue.
For inspection, defect, nonconformance, corrective action, audit, and document-history lookup, keep status, owner, priority, and change history together so the team can find the complete operating context.
In inspection execution, nonconformance classification, root-cause analysis, capa approval, effectiveness validation, and closure handling, connect assignment, approval or rejection, exception handling, and completion confirmation as one accountable workflow.
Use defect rate, nonconformance, capa due date, audit, and cost-of-quality reporting to track due dates, bottlenecks, exceptions, and completion outcomes by team, period, and operating category.
Set the role-based access, audit history, notifications, and external-system boundaries that Quality Management System (QMS) needs to operate safely.
The download opens in a browser without setup. Compare the PRD, feature specification, screen structure, and user flow with the work your team does today.
Write down real user roles, required data, approval rules, exceptions, and success metrics. Start with the core flow from quality standard, inspection plan, inspection result, nonconformance, and capa registration through inspection execution, nonconformance classification, root-cause analysis, capa approval, effectiveness validation, and closure handling.
Attach the SOT JSON in Claude or Codex with the VibeSpec plugin and describe the change in plain language. VibeSpec keeps requirements, features, screens, and user flows connected.
Replace the template vocabulary, states, and classification with the terms your team uses. Keep quality standard, inspection plan, inspection result, nonconformance, and capa registration and inspection, defect, nonconformance, corrective action, audit, and document-history lookup consistent.
Define who registers, reviews, approves, processes, and confirms completion, plus the conditions that trigger rejection or reprocessing in inspection execution, nonconformance classification, root-cause analysis, capa approval, effectiveness validation, and closure handling.
Decide what defect rate, nonconformance, capa due date, audit, and cost-of-quality reporting should measure, then connect any SSO, messaging, or adjacent-system integration to the related screens and user flow.
Create a separate Quality Management System (QMS) initiative for due-date alerts, owner assignment, approval reminders, and exception follow-up.
Before connecting Quality Management System (QMS) to source data or adjacent systems, define synchronization cadence, failure handling, access boundaries, and audit records.
Extend Quality Management System (QMS) with team, period, and category analysis plus action rules for deteriorating completion or service levels.
Adapt this Quality Management System (QMS) for our team. Ask about our user roles, states, required fields, and approval steps first, then update the requirements, screens, and user flows together.Reduce this Quality Management System (QMS) to an MVP that keeps quality standard, inspection plan, inspection result, nonconformance, and capa registration, inspection, defect, nonconformance, corrective action, audit, and document-history lookup, and inspection execution, nonconformance classification, root-cause analysis, capa approval, effectiveness validation, and closure handling. Move automation and external integrations into separate initiatives.Create a separate initiative on top of this Quality Management System (QMS) for due-date alerts and automatic owner assignment. Keep the connection to the existing screens and user flow.Yes. The complete HTML opens in a browser for review and sharing. To adapt the plan, attach the SOT JSON to Claude or Codex with the VibeSpec plugin and describe the change in plain language.
It includes quality standard, inspection plan, inspection result, nonconformance, and capa registration, inspection, defect, nonconformance, corrective action, audit, and document-history lookup, inspection execution, nonconformance classification, root-cause analysis, capa approval, effectiveness validation, and closure handling, and defect rate, nonconformance, capa due date, audit, and cost-of-quality reporting, plus foundations for access, audit history, notifications, and integrations.
The HTML is a complete planning document for reading and sharing. The SOT JSON is source data that VibeSpec can update while keeping requirements, features, screens, and user flows connected.
For a discrete capability such as automation, integration, or additional analytics, create and review a separate initiative before changing the product plan broadly.
WORKFLOW