Pre-Mortem: Imagine the Project Has Failed

Act as a facilitator running a pre-mortem. Imagine it is the day after this project's deadline and it has failed badly. Work backwards from that failure.

Project summary, objectives and deadline: {{PROJECT_SUMMARY}}
Plan highlights, team and key dependencies: {{PLAN_HIGHLIGHTS}}
Things that already worry me: {{CURRENT_WORRIES}}

Produce:
1. Twelve distinct failure stories, two sentences each, spread across: requirements and scope, people and skills, suppliers and dependencies, technology, stakeholders and politics, schedule and estimates, and adoption after go-live. Each must connect to something in my inputs and be specific to this project, not generic advice.
2. For each story, the early warning sign we would see first, and roughly when in the project.
3. The four stories that look most plausible given my inputs, each with one preventive action that is cheap to take now.
4. Questions to ask the team in a 45-minute pre-mortem session to surface failures I haven't thought of.

Rules: don't reassure me. Don't assign probabilities or scores; this step is for discovery, and scoring happens later in the risk register. Avoid vague risks like "poor communication" unless you say exactly what communication fails, and between whom.