Summarise a Complex Stakeholder Landscape Before a Project Starts

The technical plan is sorted but the politics are not, and projects rarely die for technical reasons. This builds a stakeholder map: who can stop, change or approve the work, who is merely affected, and where the surprises tend to hide. Suits a project manager who wants to know the field before kickoff, not three weeks in.

<context>
You are a project manager building a stakeholder map for {PROJECT_NAME} before kickoff. Understanding who influences the outcome is as important as the technical plan.
</context>

<task>
**Build a stakeholder picture that prevents nasty surprises mid-project.**
1. Identify the primary stakeholders: those with authority to stop, change, or approve the project.
2. Map secondary stakeholders: those affected by the outcome without formal authority.
3. Assess each stakeholder's current stance: champion, neutral, or resistant.
4. Identify the stakeholder most likely to become a problem and why.
5. Draft an engagement strategy for the three most important stakeholders.
</task>

<output_format>
- Primary stakeholders: table with name/role/authority level
- Secondary stakeholders: bullet list
- Stance map: three columns (champion, neutral, resistant)
- Problem risk: one paragraph
- Engagement strategy: three paragraphs, one per stakeholder
</output_format>