
Infotainment Feature Requirements Analyzer
Analyze infotainment feature requirements and competitive capabilities for connected vehicles
What You Can Do
You can rapidly analyze infotainment feature requests by decomposing user needs into technical specifications, mapping competitive capabilities across platforms (Apple CarPlay, Android Auto, native OEM systems), and evaluating feasibility against hardware constraints, connectivity requirements, and automotive safety standards. Claude generates structured PRD frameworks with clear trade-offs between user experience, technical integration complexity, regulatory compliance, and business investment.
Features
breaks user-requested features into discrete technical specifications and acceptance criteria aligned with automotive constraints
analyzes feature parity across Apple CarPlay, Android Auto, native OEM systems, and aftermarket solutions to identify differentiation opportunities
evaluates integration points, processing requirements (cloud vs. on-device), connectivity dependencies, and performance impact on vehicle systems
cross-references infotainment features against automotive standards (ISO 26262, SOTIF, regional homologation rules) and human-machine interface guidelines
produces structured product requirements documents with feature scope, use cases, success metrics, stakeholder dependencies, and development effort estimates
identifies business and technical trade-offs (e.g., responsiveness vs. data privacy, native capability vs. cloud dependency, development cost vs. time-to-market)
scores feature requests against feasibility, competitive impact, user demand, and technical risk to guide product planning decisions
Example Output
Example 1: Apple CarPlay Deep Integration Analysis
Feature Request: Enable full vehicle climate and seat controls through CarPlay
Decomposed Requirements:
- CAN bus message routing from vehicle HVAC controller to infotainment head unit
- Apple's CarPlay API support for proprietary vehicle control extensions (not standard)
- Low-latency responsiveness requirement (< 200ms)
- Safety-critical failsafe for manual override
Feasibility Assessment: ⚠️ Medium risk — requires Apple API partnership, custom OEM implementation, ISO 26262 ASIL B certification of control pathway
Recommended Approach: Phased rollout starting with read-only climate display (low risk), then investigate Apple partner program for write-capable APIs in future iOS versions
Example 2: Competitive Feature Matrix
| Feature | Tesla | Lucid | BMW iDrive | Our Gap |
|---|---|---|---|---|
| Real-time traffic rerouting | Native + cloud | Native + cloud | Maps integration | Behind — needs cloud partnership |
| Voice control scope | 200+ commands | 150+ commands | 80+ commands | At parity |
| OTA updates frequency | Weekly | Bi-weekly | Monthly | Leading |
Investment Recommendation: Real-time traffic rerouting closes competitive gap; requires HERE/TomTom cloud partnership (3-6 month integration)
What's Included
- SKILL.md instruction file: complete methodology for requirements decomposition, competitive mapping, and feasibility assessment
- Requirements Decomposition Template: structured worksheet breaking user needs into technical specs, constraints, and acceptance criteria
- Competitive Capability Matrix: spreadsheet comparing features across 5+ infotainment platforms and ecosystems
- Technical Feasibility Checklist: assessment framework covering CAN/vehicle network integration, connectivity (5G/WiFi), cloud dependencies, safety compliance, and OTA update considerations
- PRD Framework Scaffold: structured product requirements document template with feature scope, use cases, success metrics, stakeholder dependencies, and risk assessment
Who It's For
- Connected car product managers defining infotainment roadmaps and feature priorities
- Automotive UX/UI designers translating user needs into technically feasible product specifications
- Vehicle engineering teams assessing integration complexity and system impact of new features
- Product marketing managers positioning infotainment capabilities against competitors
- Strategic planners evaluating feature investment ROI and time-to-market trade-offs
Best For
- Analyzing customer feature requests and translating them into actionable requirements
- Competitive analysis of infotainment capabilities across Apple CarPlay, Android Auto, Tesla, BMW, Mercedes, and other OEM platforms
- Feasibility assessment of cloud-native vs. on-device feature architecture decisions
- Building business cases and development roadmaps with hardware and connectivity constraints
- Regulatory and safety compliance review for human-machine interface features
- Stakeholder alignment workshops between product, engineering, UX, and vehicle connectivity teams







