FREE CLAUDE & CODEX PLUGIN TEMPLATE
A real SOT-based Customer Health Score Management System PRD template connecting customer goal, usage signal, health criterion, and risk-factor registration, health score, activation, usage, owner, risk, and action-history lookup, signal collection, score calculation, risk review, success plan, customer touchpoint, and impact validation, health distribution, churn risk, activation, renewal, and action-impact reporting.
View source on GitHub · MIT licensed
USE CASE
Teams designing an internal operations system for customer-success manager tracking relationships and product use and customer success and retention 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 Customer Health Score Management System connects customer goal, usage signal, health criterion, and risk-factor registration, health score, activation, usage, owner, risk, and action-history lookup, signal collection, score calculation, risk review, success plan, customer touchpoint, and impact validation, and health distribution, churn risk, activation, renewal, and action-impact 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 customer goal, usage signal, health criterion, and risk-factor registration, define the required context, classification rules, and duplicate or missing-data checks before work enters the operating queue.
For health score, activation, usage, owner, risk, and action-history lookup, keep status, owner, priority, and change history together so the team can find the complete operating context.
In signal collection, score calculation, risk review, success plan, customer touchpoint, and impact validation, connect assignment, approval or rejection, exception handling, and completion confirmation as one accountable workflow.
Use health distribution, churn risk, activation, renewal, and action-impact 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 Customer Health Score Management System 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 customer goal, usage signal, health criterion, and risk-factor registration through signal collection, score calculation, risk review, success plan, customer touchpoint, and impact validation.
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 customer goal, usage signal, health criterion, and risk-factor registration and health score, activation, usage, owner, risk, and action-history lookup consistent.
Define who registers, reviews, approves, processes, and confirms completion, plus the conditions that trigger rejection or reprocessing in signal collection, score calculation, risk review, success plan, customer touchpoint, and impact validation.
Decide what health distribution, churn risk, activation, renewal, and action-impact reporting should measure, then connect any SSO, messaging, or adjacent-system integration to the related screens and user flow.
Create a separate Customer Health Score Management System initiative for due-date alerts, owner assignment, approval reminders, and exception follow-up.
Before connecting Customer Health Score Management System to source data or adjacent systems, define synchronization cadence, failure handling, access boundaries, and audit records.
Extend Customer Health Score Management System with team, period, and category analysis plus action rules for deteriorating completion or service levels.
Adapt this Customer Health Score Management System 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 Customer Health Score Management System to an MVP that keeps customer goal, usage signal, health criterion, and risk-factor registration, health score, activation, usage, owner, risk, and action-history lookup, and signal collection, score calculation, risk review, success plan, customer touchpoint, and impact validation. Move automation and external integrations into separate initiatives.Create a separate initiative on top of this Customer Health Score Management System 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 customer goal, usage signal, health criterion, and risk-factor registration, health score, activation, usage, owner, risk, and action-history lookup, signal collection, score calculation, risk review, success plan, customer touchpoint, and impact validation, and health distribution, churn risk, activation, renewal, and action-impact 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