FREE CLAUDE & CODEX PLUGIN TEMPLATE
A real SOT-based Manufacturing Execution System (MES) PRD template connecting item, bill of materials, process, work order, and quality-standard registration, production plan, work progress, equipment, defect, work-in-progress, and shipment-history lookup, work-order release, process execution, output collection, quality inspection, exception action, and completion handling, production volume, defect rate, process lead time, equipment utilization, delivery, and traceability reporting.
View source on GitHub · MIT licensed
USE CASE
Teams designing an internal operations system for shop-floor worker and production manager managing work orders and process output and production operations and smart-factory 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 Manufacturing Execution System (MES) connects item, bill of materials, process, work order, and quality-standard registration, production plan, work progress, equipment, defect, work-in-progress, and shipment-history lookup, work-order release, process execution, output collection, quality inspection, exception action, and completion handling, and production volume, defect rate, process lead time, equipment utilization, delivery, and traceability 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 item, bill of materials, process, work order, and quality-standard registration, define the required context, classification rules, and duplicate or missing-data checks before work enters the operating queue.
For production plan, work progress, equipment, defect, work-in-progress, and shipment-history lookup, keep status, owner, priority, and change history together so the team can find the complete operating context.
In work-order release, process execution, output collection, quality inspection, exception action, and completion handling, connect assignment, approval or rejection, exception handling, and completion confirmation as one accountable workflow.
Use production volume, defect rate, process lead time, equipment utilization, delivery, and traceability 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 Manufacturing Execution System (MES) 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 item, bill of materials, process, work order, and quality-standard registration through work-order release, process execution, output collection, quality inspection, exception action, and completion 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 item, bill of materials, process, work order, and quality-standard registration and production plan, work progress, equipment, defect, work-in-progress, and shipment-history lookup consistent.
Define who registers, reviews, approves, processes, and confirms completion, plus the conditions that trigger rejection or reprocessing in work-order release, process execution, output collection, quality inspection, exception action, and completion handling.
Decide what production volume, defect rate, process lead time, equipment utilization, delivery, and traceability reporting should measure, then connect any SSO, messaging, or adjacent-system integration to the related screens and user flow.
Create a separate Manufacturing Execution System (MES) initiative for due-date alerts, owner assignment, approval reminders, and exception follow-up.
Before connecting Manufacturing Execution System (MES) to source data or adjacent systems, define synchronization cadence, failure handling, access boundaries, and audit records.
Extend Manufacturing Execution System (MES) with team, period, and category analysis plus action rules for deteriorating completion or service levels.
Adapt this Manufacturing Execution System (MES) 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 Manufacturing Execution System (MES) to an MVP that keeps item, bill of materials, process, work order, and quality-standard registration, production plan, work progress, equipment, defect, work-in-progress, and shipment-history lookup, and work-order release, process execution, output collection, quality inspection, exception action, and completion handling. Move automation and external integrations into separate initiatives.Create a separate initiative on top of this Manufacturing Execution System (MES) 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 item, bill of materials, process, work order, and quality-standard registration, production plan, work progress, equipment, defect, work-in-progress, and shipment-history lookup, work-order release, process execution, output collection, quality inspection, exception action, and completion handling, and production volume, defect rate, process lead time, equipment utilization, delivery, and traceability 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