Service offering and eligibility
Define the policy, owner, required data, and exception criteria for service offering and eligibility, then connect it to the next operating decision.
FREE CLAUDE & CODEX PLUGIN TEMPLATE
A real SOT-based IT Service Catalog and Request Management System PRD template connecting service-catalog search and request submission, service, request, approval, and fulfillment-status lookup, request triage, approval, fulfillment, sla, and completion confirmation, service demand, fulfillment time, sla, and automation-rate reporting.
View source on GitHub · MIT licensed
USE CASE
Teams designing an internal operations system for employee requesting an it service and it service delivery 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 service catalog PRD Template connects service offering and eligibility, request forms and required data, fulfillment ownership and sla, and service demand and performance reporting in one operating source of truth that teams can review and extend with VibeSpec.
Define the policy, owner, required data, and exception criteria for service offering and eligibility, then connect it to the next operating decision.
Define the policy, owner, required data, and exception criteria for request forms and required data, then connect it to the next operating decision.
Define the policy, owner, required data, and exception criteria for fulfillment ownership and sla, then connect it to the next operating decision.
Define the policy, owner, required data, and exception criteria for service demand and performance reporting, then connect it to the next operating decision.
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.
Set the real team roles, approval rules, change and exception handling, and success measures before expanding the flow from service offering and eligibility through fulfillment ownership and sla.
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 service catalog PRD Template states, object names, owners, and approvers with the language your team actually uses.
Connect rework, approval, and evidence-retention rules for nonstandard cases to fulfillment ownership and sla.
Define service demand and performance reporting metrics together with source-data ownership and integration failure handling.
Extend service catalog PRD Template with a separate initiative for deadline, risk, and exception alerts.
Define synchronization, permissions, audit records, and recovery behavior before integration.
Extend service demand and performance reporting with team, period, and category analysis plus action thresholds.
Adapt this service catalog PRD Template for our team. Ask about roles, states, policies, approvals, exceptions, and metrics first, then update requirements, screens, and flows together.Reduce this service catalog PRD Template to an MVP focused on service offering and eligibility, request forms and required data, and fulfillment ownership and sla, with automation and integrations as separate initiatives.Create an automation initiative on top of this service catalog PRD Template for risk alerts and owner follow-up.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 service offering and eligibility, request forms and required data, fulfillment ownership and sla, service demand and performance reporting, and the operating foundations for roles, access, audit, 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