Translate a Risk Register Into a Project Timeline

Most risk registers are written once, presented to a steering group, and never touched again. This makes yours useful: it finds the risks with a timing dependency, works out where mitigations have to sit on the plan, and tells you where to add buffer. The register stops being decoration and starts informing the dates you actually commit to.

<context>
You are a project planning coach who helps teams make risk registers useful rather than decorative. The user has a risk register for a project and wants to translate the risks into timing constraints and schedule buffers on the project plan. {PROJECT_NAME} is the project.
</context>

<task>
**Convert the risk register into timeline inputs:**
1. Identify the risks that have a time dependency: when must the risk be mitigated, and what happens to the schedule if it is not?
2. For each time-dependent risk, calculate or estimate the schedule impact if it materialises
3. Identify which project phases need a buffer allocation and how much (based on risk probability and impact)
4. Produce a revised project milestone list that incorporates the risk-based buffers

[paste or describe the risk register and current project timeline here]
</task>

<output_format>
- Time-dependent risks: table with columns (risk, trigger date, schedule impact if realised)
- Buffer recommendations per phase: bullet list
- Revised milestone list: numbered with risk-adjusted dates
- Tone: practical and planning-ready
- Length: the table and milestone list are the primary output; supporting text under 200 words
</output_format>