
Infotainment Feature Requirements Architect
Define connected car infotainment features with OEM, UX, and compliance rigor
What You Can Do
You systematically architect feature requirements for connected car infotainment systems by synthesizing customer insights, technical constraints, and regulatory mandates. This skill structures the translation of market data into unambiguous specifications that engineering teams can execute against, accounting for legacy hardware integration, multi-generational vehicle platforms, and safety-critical certification requirements.
Features
Example Output
Example 1: Voice Command Feature Specification
Feature: Natural Language Voice Control for Navigation Destination Input
User Requirement: Driver can speak destination name naturally without phrase templates
Technical Constraint: Processor supports 100ms latency; no cloud connectivity in cellular dead zones
Compliance Impact: ISO 26262 ASIL-B for distraction risk; SOTIF hazard for misheard commands
Specification Output:
- Fallback behavior: Transitions to keyboard input if ASR confidence <75%
- Safety interlock: Voice input blocked during emergency maneuvers (airbag deploy, hard braking)
- Regulatory mapping: Drives down maximum speech interaction duration to 15 seconds per SAE J2699
Example 2: App Integration Feature Matrix
| App Category | Model Year Support | Hardware Requirement | Compliance Barrier | Ship Status |
|---|---|---|---|---|
| Music Streaming | MY24–MY27 | 512MB RAM min | GDPR data residency | Phase 1 |
| Navigation | MY22+ | LTE modem | SOTIF OTA update validation | Approved |
| Vehicle Diagnostics | MY25+ | CAN-FD gateway | ISO 26262 medical-device-grade logging | Design phase |
What's Included
- SKILL.md instruction file with full requirements architecture methodology:
- Feature Requirements Template: structured format for capability, constraints, compliance, and acceptance criteria
- Compliance Mapping Checklist: automotive standards cross-reference (ISO 26262, SOTIF, GDPR, SAE J2699)
- Hardware Capability Matrix: baseline constraints by infotainment platform generation
- Multi-Generational Feasibility Workflow: process for assessing feature backward compatibility across model years
Who It's For
- Connected car product managers defining infotainment roadmaps and feature priorities
- Automotive UX designers translating user research into specifications for development handoff
- Requirements engineers on OEM product teams balancing stakeholder demands with technical reality
- Compliance and functional safety leads embedding regulatory constraints into feature definitions
- Infotainment platform teams evaluating third-party capabilities against internal product strategy
Best For
- Defining feature specifications before engineering sprints to eliminate ambiguity and rework
- Reconciling conflicting priorities (safety vs. UX richness, marketing features vs. feasibility) with structured frameworks
- Assessing features for multi-generational vehicle lineup support with hardware variance
- Building compliance traceability matrices linking user needs to automotive standards
- Documenting interaction flows for complex multi-modal features (voice + touch + steering wheel controls)







