Enterprise Plugin Lifecycle and Sunset Governance Framework

Role: Marketplace Product Operations Strategist specializing in catalog governance and developer ecosystem lifecycle management.

Context

• Host ecosystem: {{software_suite}}
• Architecture classification: {{plugin_type}}
• Minimum performance metric: {{active_user_threshold}}
• Sunsetting notice timeline: {{deprecation_window}}
• Operational maintenance tier: {{support_level}}
• Regulatory benchmark: {{compliance_standard}}

Task

Create an operational framework to systematically audit catalog health, identify non-compliant or dormant extensions, and manage graceful deprecations across the marketplace.

Method

1. Establish routine health audit metrics tracking usage against {{active_user_threshold}} and technical compliance with {{compliance_standard}}.
2. Define categorization criteria for extensions: Healthy, At-Risk, Inactive, and Security Non-Compliant.
3. Outline automated outreach sequences triggered when a {{plugin_type}} drops below vital benchmarks.
4. Formulate the official deprecation staging workflow, setting milestone timelines adhering to {{deprecation_window}}.
5. Detail customer-facing notification protocols and migration guidance toward alternative catalog solutions.
6. Specify the runtime containment procedures (e.g., delisting, disabling API credentials, revoking tokens).
7. Establish the archival, customer data deletion, and post-mortem review standards.

Constraints

• MUST define explicit timelines matching {{deprecation_window}} for every wind-down phase.
• MUST NOT allow extensions violating {{compliance_standard}} to remain listed during grace periods.
• Maintenance obligations MUST strictly align with {{support_level}}.
• Provide concrete action triggers rather than vague guidance.

Output format

Provide the governance framework structured in 4 sequential components:

1. Health Metric & Classification Index: Thresholds and risk flags.
2. Vendor Intervention Protocol: Communication stages and remediation timelines.
3. Sunset & Deprecation Pipeline: Phase-by-phase retirement procedures.
4. Migration & Data Security Policy: Customer protection and artifact cleanup rules. Keep the output concise, structured, and under 600 words.

Self-review

• Ensure all variables ({{software_suite}}, {{plugin_type}}, {{active_user_threshold}}, {{deprecation_window}}, {{support_level}}, {{compliance_standard}}) are logically integrated.
• Confirm the method contains distinct, non-overlapping operational steps.
• Check that compliance and data safety guardrails are unambiguous.