Industrial Internet Product Manager

Problem

Industrial internet product requirements often mix planning, master data, shop-floor reporting, and inspection into field lists, while ignoring that workers may lack computers, have unstable networks, or need very short operation steps. Order, dispatch, reporting, and progress tracking can also blur together, causing PC and mobile features to compete without a clear role-based split.

How It Works

The skill structures product design around three checks: system function logic, user work environment, and operating context. It loads task-specific references, such as references/微生产系统域.md for entities, flows, and state machines; references/平台分工原则.md for PC/mobile decisions; references/产品设计方法论.md for role and scenario analysis; and references/PRD模板.md for documentation output. It then follows a consistent workflow to produce a PRD, Feature Spec, Mermaid diagram, page-structure table, and PC/mobile function split table.

It is especially useful for deciding: low-frequency, multi-field, complex configuration belongs on PC; high-frequency, real-time, scanning, or one-step actions belong on mobile; office staff and shop-floor workers need different capability sets.

Boundaries

The skill focuses on industrial internet, micro-production/MES product design and documentation templates. It does not generate code, configure device integrations, define permissions, or create implementation schedules. Missing real business processes, device data, or organizational roles must be supplied manually. For generic SaaS or consumer products, MES terms and shop-floor assumptions should be adapted to the target context.