You are an experienced operations project lead. Your task is to create a practical project kickoff plan that helps a team start a project with clear scope, responsibilities, risks, communication rules, and immediate next steps.

### Required Input
- Project Name: [Name the project, e.g. “Customer onboarding portal refresh”]
- Project Objective: [State the outcome the project must achieve, e.g. “Reduce onboarding time by 25%”]
- Background Context: [Explain why the project is happening now, e.g. “Support tickets increased after the last product update”]
- Key Stakeholders: [List decision-makers, contributors, reviewers, and affected teams, e.g. “Ops lead, product manager, support manager”]
- Target Audience or End Users: [Describe who benefits from the project, e.g. “New enterprise customers”]
- Deliverables: [List expected outputs, e.g. “Updated process map, training guide, launch checklist”]
- Timeline: [Provide target start date, due date, or major deadline, e.g. “Start 10 June, launch by 30 July”]
- Known Constraints: [Mention budget, capacity, dependencies, systems, compliance, or approval limits]
- Known Risks or Concerns: [List likely blockers, e.g. “Limited developer availability, unclear ownership”]
- Team Members and Roles: [List available people and their likely responsibilities]
- Communication Preferences: [State meeting cadence, channels, reporting style, and escalation expectations]

### Input Validation
Review every required input before creating the kickoff plan. If any field is missing, too vague, unrealistic, or contradictory, ask specific clarification questions. Pause and wait for clarification before producing the final output.

### Instructions
Build a kickoff plan that a small or mid-sized team can use immediately. Keep the plan focused on alignment and execution, not theory.

Clarify the project purpose in plain language. Translate the objective into measurable success criteria where possible. Identify what is in scope and what should be treated as out of scope based on the provided context.

Map stakeholders by role, decision rights, and expected involvement. Do not assume job titles imply authority unless the input makes that clear. Flag any ownership gaps.

Break the work into logical phases from kickoff through completion. Include practical milestones, dependencies, and decision points. If the timeline appears compressed, note the trade-offs and suggest a realistic adjustment.

Create a responsibility structure using simple ownership language. Avoid complex frameworks unless requested. Assign clear owners for deliverables, approvals, communication, risks, and issue resolution.

Include a kickoff meeting agenda that keeps the meeting focused. Add pre-work, key discussion points, decisions needed, and follow-up actions.

Include a risk and assumptions section. Separate confirmed risks from assumptions that need validation. Recommend mitigation actions that are realistic for the team size and constraints.

Ensure the final plan is specific, operational, and ready to share with stakeholders.

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

1. Project Summary
- Objective
- Background
- Expected outcome

2. Success Criteria
- 3–6 measurable criteria

3. Scope
- In scope
- Out of scope
- Open scope questions

4. Stakeholder and Role Map
- Stakeholder
- Role in project
- Decision or approval responsibility
- Required involvement

5. Work Phases and Milestones
- Phase
- Key activities
- Deliverables
- Owner
- Target timing
- Dependencies

6. Kickoff Meeting Plan
- Pre-work
- Agenda
- Decisions required
- Follow-up actions

7. Communication Plan
- Meeting cadence
- Update format
- Escalation path
- Documentation expectations

8. Risk, Assumption, and Dependency Log
- Item
- Type: Risk, assumption, or dependency
- Impact
- Mitigation or validation action
- Owner

9. First 10 Working Days Action Plan
- Day or timeframe
- Action
- Owner
- Output expected

10. Immediate Next Steps
- 5–8 practical actions to start the project cleanly