制定跨平台功能同步规划
按各平台使用场景制定功能覆盖原则、跟进时限与差距台账,明确负责人和规划流程。
完整提示词
<context>
You set a standing policy for how features reach each platform when a product ships on web, iOS, Android and sometimes desktop. Without one, each platform team plans separately, gaps grow, customers on one platform feel neglected, support has to explain why something works on the web but not on the phone, and every roadmap meeting re-argues whether a feature must launch everywhere at once. Full parity for everything is expensive and often wrong: people use each platform for different jobs (mobile for quick checks and capture, web for setup and heavy editing). A good policy classifies features (core flows that must match, platform-specific features that fit one context, admin or power features that can stay on one platform), names which platform leads for each class, sets the maximum acceptable lag, and keeps parity gaps visible as debt with owners.
</context>
<task>
Platforms:
<platforms>
{{platforms}}
</platforms>
Current state:
<current_state>
{{current_state}}
</current_state>
1. Summarise usage by platform from the data given: who uses which platform for what. If data is missing, say what to measure.
2. Write three to five parity principles in plain language, tied to how this product is used.
3. Define feature classes with a parity target each: for example core flows (all platforms, within a short lag), contextual features (only where they fit), and admin or power features (one platform is enough). Give examples from the user's product.
4. Set lead-platform rules: which platform leads for each class and why, the maximum lag for followers, and what happens to features that miss it.
5. Build a parity debt register from the current gaps: feature, missing platforms, class, user impact, decision (close, accept, or remove from the leading platform), and owner.
6. Recommend planning changes: how parity is checked during roadmap planning, how specs cover each platform, and how often the debt register is reviewed.
</task>
<constraints>
- Use only the usage and team data given; do not invent platform shares.
- Do not default to "full parity everywhere"; justify each target by how users actually use the platform.
- Platform store rules and technical limits can make some features impossible or different on a platform; note where to check rather than assuming.
{{> output/uncertainty}}
</constraints>
<output_format>
## Usage by platform
Bullets.
## Parity principles
Numbered list.
## Feature classes and targets
Table: class | definition | examples | parity target | max lag.
## Lead platform rules
Bullets.
## Parity debt register
Table: feature | missing on | class | user impact | decision | owner.
## Planning changes
Bullets.
</output_format>可替换内容
- {{platforms}}
- {{current_state}}
- {{> output/uncertainty}}
分类与标签
办公效率、产品规划、跨平台协作、功能差距、责任台账