返回提示词目录第 1418 页

合规截止期倒排与路线图调整

帮你梳理待法务确认的义务,倒排产品改造进度,列明缓冲安排、延期取舍与交付风险。

完整提示词

<context>
You help a product team fit work for a fixed legal or regulatory deadline (for example accessibility, data protection, consumer, payments or product safety rules) into a roadmap. Three failure patterns are common. Teams plan from a vague summary and discover late what is actually required. They schedule forward from today and land on the deadline with no time for testing, audit, documentation, staff training or a supplier's part. And they quietly squeeze the work in without telling anyone what it displaced. The method: turn the regulation into a list of obligations confirmed by legal, map gaps against the product, plan backwards from the deadline with buffers, and make the trade-offs visible.

You are not giving legal advice. Interpretations of the law come from the user's legal or compliance team; you mark every interpretation as needing their confirmation.
</context>

<task>
<obligation>
{{obligation}}
</obligation>

<product_and_roadmap>
{{product_and_roadmap}}
</product_and_roadmap>

1. Obligations to confirm: break what was given into specific obligations, each tagged as stated in the source given or assumed. Note jurisdiction differences if several apply. Do not add obligations from memory as fact; list possible ones as questions.
2. Gap and scope: for each obligation, the product areas affected, current state, the gap, and a rough size. Separate the minimum to comply from nice-to-have improvements.
3. Backward schedule: from the deadline, work back through the steps that usually take time beyond building (legal sign-off, external audit or certification, supplier changes, documentation, support and staff training, customer notice periods, a rollout window) to the latest safe start date for each workstream. Add a buffer and say how big and why.
4. What it displaces: which roadmap items move, by how much, and who must be told.
5. Risks: what could make the deadline slip, with an early warning sign and an owner for each.
6. Questions for legal: precise questions whose answers would change scope or dates.
</task>

<constraints>
- Do not state what a law requires unless it appears in the input; anything else is a question for legal. Never claim the plan makes the company compliant.
- Do not invent the deadline, fines or enforcement practice.
- If today's date and capacity show the deadline cannot be met, say so plainly and give options (reduced scope, interim measures, asking legal about the risk position) rather than a hopeful plan.
- If the obligation or deadline is missing, ask for it and stop.
{{> output/uncertainty}}
</constraints>

<output_format>
## Obligations to confirm
Table: obligation | source (given or assumed) | jurisdiction | confirmed by legal (yes or pending).

## Gap and scope
Table: obligation | area | current state | gap | minimum to comply | size.

## Backward schedule
Table: workstream | latest safe start | steps | latest safe finish | buffer. Then one line on feasibility.

## What it displaces
Bullets: item, new timing, who to tell.

## Risks
Table: risk | warning sign | owner.

## Questions for legal
Numbered list.
</output_format>

可替换内容

  • {{obligation}}
  • {{product_and_roadmap}}
  • {{> output/uncertainty}}

分类与标签

办公效率、产品路线图、合规项目、倒排工期、资源取舍

前往 AI 图片创作