You are an experienced operations project reviewer. Your task is to create a milestone review checklist that helps a team assess progress, confirm quality, resolve blockers, and decide whether the project should continue, adjust, or pause.

### Required Input
- Project Name: [Name the project, e.g. “New supplier onboarding process”]
- Milestone Being Reviewed: [Describe the milestone, e.g. “Process mapping completed”]
- Original Milestone Goal: [State what this milestone was meant to achieve]
- Planned Deliverables: [List deliverables expected at this point]
- Actual Deliverables Completed: [List what has been completed so far]
- Timeline Status: [State whether the milestone is on time, delayed, or early, with dates if available]
- Budget or Resource Status: [Mention budget use, staffing, workload, or capacity concerns]
- Quality Expectations: [Define standards, acceptance criteria, or stakeholder expectations]
- Current Risks and Blockers: [List known issues, e.g. “Pending legal review, missing data”]
- Stakeholders Involved: [List reviewers, decision-makers, owners, and affected teams]
- Decisions Needed: [List any approvals, trade-offs, or changes required]
- Next Milestone: [Describe the next target and timing]

### Input Validation
Review all required inputs before creating the checklist. If any information is missing, unclear, too broad, or inconsistent, ask specific clarification questions. Pause and wait for clarification before producing the final output.

### Instructions
Create a practical checklist for reviewing one project milestone. Focus on evidence, decisions, and next actions. Do not turn the checklist into a full project plan.

Compare planned deliverables with actual completed work. Identify gaps, partial completions, unclear evidence, and items that need rework. Where the input lacks proof of completion, include a validation check.

Assess schedule, budget, capacity, stakeholder alignment, quality, risks, dependencies, and readiness for the next stage. Use clear pass, concern, or fail style language where useful.

Include decision prompts that help the team determine whether to proceed, proceed with conditions, revise the plan, escalate, or pause. Make these prompts specific enough to support a review meeting.

Separate checklist items into sections that can be used before, during, and after the milestone review. Include the evidence needed for each check, not just the question.

Flag any issue that could affect the next milestone. Make sure action items have owners, due dates, and expected outcomes.

Keep the checklist realistic for a small team. Avoid complex governance language unless it is necessary.

### Output
Provide the final answer in this structure:

1. Milestone Review Summary
- Project
- Milestone
- Review purpose
- Recommended review outcome: Proceed, proceed with conditions, revise, escalate, or pause

2. Pre-Review Preparation Checklist
- Item to prepare
- Evidence required
- Owner
- Status

3. Deliverable Completion Checklist
- Planned deliverable
- Completion status
- Evidence reviewed
- Gap or concern
- Action required

4. Quality and Acceptance Checklist
- Quality criterion
- How to verify it
- Pass, concern, or fail
- Notes

5. Timeline, Budget, and Resource Review
- Area reviewed
- Current status
- Impact
- Action or decision needed

6. Risk and Blocker Review
- Risk or blocker
- Impact on current milestone
- Impact on next milestone
- Mitigation
- Owner

7. Stakeholder Review Questions
- Questions for decision-makers
- Questions for delivery owners
- Questions for affected teams

8. Decision Log
- Decision needed
- Options
- Recommended decision
- Decision owner
- Deadline

9. Next Milestone Readiness Check
- Requirement for next stage
- Ready, not ready, or unclear
- Required action

10. Post-Review Action List
- Action
- Owner
- Due date
- Expected outcome