Analyze and prioritize feature requests from Autostay subscribers, app reviews, and partner feedback by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging subscriber VOC, or making prioritization decisions.
From autostay-pmnpx claudepluginhub autostay-kr/autostay-skills --plugin autostay-pmThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Categorize, evaluate, and prioritize feature requests from Autostay subscribers, app store reviews, and partner feedback against product goals.
Autostay — O2O 세차 구독 서비스
Never allow customers to design solutions. Prioritize opportunities (problems), not features. Use Opportunity Score (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance x (1 - Satisfaction), normalized to 0-1. See the prioritization-frameworks skill for full details and templates.
You are analyzing feature requests for $ARGUMENTS in the context of Autostay's car wash subscription service.
If the user provides files (spreadsheets, CSVs, app store reviews, VOC data, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.
When categorizing requests, use these Autostay-specific theme categories:
| Theme | Description | Examples |
|---|---|---|
| 예약 경험 | Booking flow, scheduling, availability, rescheduling | 예약 시간대 확대, 당일 예약, 예약 변경 편의성 |
| 세차 품질 | Wash quality, service options, detailing, damage | 세차 품질 균일화, 코팅 옵션, 세차 전후 사진 |
| 구독 가치 | Subscription plans, pricing, benefits, upgrades | 요금제 다양화, 가족 구독, 구독 혜택 확대 |
| 파트너 경험 | Partner tools, onboarding, revenue, operations | 파트너 대시보드, 정산 투명성, 운영 도구 |
| 결제/빌링 | Payment methods, billing, refunds, pricing | 결제 수단 추가, 자동 결제, 환불 프로세스 |
| 앱 UX | App navigation, notifications, account management | 앱 속도 개선, 알림 설정, UI 개선 |
Requests may span multiple themes. Assign a primary theme and note secondary themes when applicable.
The user will describe their product goal and provide feature requests (subscriber VOC, app reviews, partner feedback, or a mix). Work through these steps:
Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization. Reference Autostay metrics (MRR, Churn Rate, LTV, NPS).
Identify the source: Tag each request by source type:
Categorize requests into Autostay themes: Group related requests using the theme categories above. Name each group clearly.
Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals and Autostay's subscription growth objectives.
Prioritize the top 3 features based on:
For each top feature, provide:
Think step by step. Save as markdown or create a structured output document.